<details> <summary><strong>Sister projects from n24q02m</strong> (click to expand)</summary>
The server publishes 7 tools. What each one is for:
message — send, edit, delete, forward, pin, react, search, historychat — list, info, create, join, leave, members, admin, settings, topicsmedia — send_photo, send_file, send_voice, send_video, downloadcontact — list, search, add, blockconfig — status, set, cache_clear, setup_status, setup_start, setup_reset, setup_completehelp — --config__open_relay — --Configuration is passed through the environment: TELEGRAM_BOT_TOKEN, PUBLIC_URL, MCP_DCR_SERVER_SECRET, DCR_SERVER_SECRET, TELEGRAM_API_ID, YOUR_ACCOUNT_ID, ACCOUNT_ID, YOUR_PUBLIC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Better Telegram MCP's toolset — message, chat, media and 4 more — is a fair guide to whether it matches your workflow. It is maintained by n24q02m; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| message | send, edit, delete, forward, pin, react, search, history |
| chat | list, info, create, join, leave, members, admin, settings, topics |
| media | send_photo, send_file, send_voice, send_video, download |
| contact | list, search, add, block |
| config | status, set, cache_clear, setup_status, setup_start, setup_reset, setup_complete |
| help | -- |
| config__open_relay | -- |
{
"mcpServers": {
"better-telegram": {
"command": "uvx",
"args": ["invocation"],
"env": {
"TELEGRAM_BOT_TOKEN": "your-value",
"PUBLIC_URL": "your-value",
"MCP_DCR_SERVER_SECRET": "your-value",
"DCR_SERVER_SECRET": "your-value",
"TELEGRAM_API_ID": "your-value",
"YOUR_ACCOUNT_ID": "your-value",
"ACCOUNT_ID": "your-value",
"YOUR_PUBLIC_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_BOT_TOKEN | Credential the server authenticates with. | Yes |
| PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_DCR_SERVER_SECRET | Credential the server authenticates with. | Yes |
| DCR_SERVER_SECRET | Credential the server authenticates with. | Yes |
| TELEGRAM_API_ID | Configuration value read at startup. | Optional |
| YOUR_ACCOUNT_ID | Configuration value read at startup. | Optional |
| ACCOUNT_ID | Configuration value read at startup. | Optional |
| YOUR_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.