agentleFS
salto-agancysalto-agancy/telegram-mcp-ai-deploy/docs/CLAUDE.md

telegram-mcp-ai-deploy

CLAUDE.md0 starsChanged 2 months agoMITView on GitHub

Copy templates/claude-code/.mcp.json.example to the project as .mcp.json, replace only the hostname, and export TELEGRAM_MCP_BEARER in a protected shell/keychain environment. Merge with an existing file—never overwrite it. Remote HTTP is preferred; SSE is legacy. OAuth is also supported by Claude Code with preconfigured client credentials, but bearer is the simplest non-browser automation path for this fixed-client deployment. Add https://HOST/mcp, open advanced authentication, and enter the values from secrets/oauth_client_id and secrets/oauth_client_secret without copying them to docs. Complete browser authorization. The standard Claude…

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add https://HOST/mcp, open advanced authentication, and enter the values from secrets/oauth_client_id and secrets/oauth_client_secret …

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Claude and Claude Code

Claude Code

Copy templates/claude-code/.mcp.json.example to the project as .mcp.json, replace only the hostname, and export TELEGRAM_MCP_BEARER in a protected shell/keychain environment. Merge with an existing file—never overwrite it. Remote HTTP is preferred; SSE is legacy.

OAuth is also supported by Claude Code with preconfigured client credentials, but bearer is the simplest non-browser automation path for this fixed-client deployment.

Claude web/desktop custom integration

Add https://HOST/mcp, open advanced authentication, and enter the values from secrets/oauth_client_id and secrets/oauth_client_secret without copying them to docs. Complete browser authorization. The standard Claude callback is already allowlisted.

Official references:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.