Telegram for AI agents: messages, chats, media, and contacts in bot and user-account modes.
Connect Runs on your machine
claude mcp add better-telegram-mcp -e TELEGRAM_BOT_TOKEN=<TELEGRAM_BOT_TOKEN> -e TELEGRAM_API_ID=<TELEGRAM_API_ID> -e TELEGRAM_API_HASH=<TELEGRAM_API_HASH> -- uvx n24q02m-telegram==4.23.0{
"mcpServers": {
"better-telegram-mcp": {
"command": "uvx",
"args": [
"n24q02m-telegram==4.23.0"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<TELEGRAM_BOT_TOKEN>",
"TELEGRAM_API_ID": "<TELEGRAM_API_ID>",
"TELEGRAM_API_HASH": "<TELEGRAM_API_HASH>"
}
}
}
}{
"mcpServers": {
"better-telegram-mcp": {
"command": "uvx",
"args": [
"n24q02m-telegram==4.23.0"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<TELEGRAM_BOT_TOKEN>",
"TELEGRAM_API_ID": "<TELEGRAM_API_ID>",
"TELEGRAM_API_HASH": "<TELEGRAM_API_HASH>"
}
}
}
}{
"servers": {
"better-telegram-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"n24q02m-telegram==4.23.0"
],
"env": {
"TELEGRAM_BOT_TOKEN": "<TELEGRAM_BOT_TOKEN>",
"TELEGRAM_API_ID": "<TELEGRAM_API_ID>",
"TELEGRAM_API_HASH": "<TELEGRAM_API_HASH>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
TELEGRAM_BOT_TOKENOptional, secret | Telegram bot token from @BotFather (for bot mode) |
TELEGRAM_API_IDOptional | Telegram API ID from my.telegram.org (for user mode) |
TELEGRAM_API_HASHOptional, secret | Telegram API hash from my.telegram.org (for user mode) |
Details
| Package | [email protected] (PYPI, stdio) |
| Package | docker.io/n24q02m/telegram:latest (OCI, stdio) |
| First published | 27 Oct 2026 |
| Last updated | 27 Oct 2026 |
| Registry name | io.github.n24q02m/better-telegram-mcp |
More communication servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.