MCP server that exposes a Telegram bot
MCP server that exposes a Telegram bot. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
TELEGRAM_BOT_TOKEN environment variableEverything the assistant can do here goes through one of these:
send_message — Send a message to a Telegram chatget_me — Get bot informationget_updates — Get recent updates from TelegramInstallation goes through your MCP client rather than a global install: point it at mcp-telegram-bot on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: TELELEGRAM_BOT_TOKEN, TELEGRAM_BOT_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — send_message, get_me, get_updates — is a fair guide to whether it matches your workflow. It is maintained by daedalus; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| send_message | Send a message to a Telegram chat |
| get_me | Get bot information |
| get_updates | Get recent updates from Telegram |
{
"mcpServers": {
"telegram-bot": {
"command": "uvx",
"args": ["mcp-telegram-bot"],
"env": {
"TELELEGRAM_BOT_TOKEN": "your-value",
"TELEGRAM_BOT_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TELELEGRAM_BOT_TOKEN | Credential the server authenticates with. | Yes |
| TELEGRAM_BOT_TOKEN | Credential the server authenticates with. | 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.