Developer · Local MCP server
Telegram MCP Server
Local-first TDLib Telegram MCP server with 115 tools, account isolation and production guardrails.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tolboy/telegram-mcp-tdlib- Version
- 1.17.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- tolboy (GitHub)
- Listed under
- Telegram MCP servers
- Repository
- github.com/tolboy/telegram-mcp-tdlib
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/tolboy/telegram-mcp-tdlib:1.17.0-stdio | — | stdio |
How to connect Telegram MCP Server
Telegram MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/tolboy/telegram-mcp-tdlib:1.17.0-stdio. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e TDLIB_API_ID -e TDLIB_API_HASH -e TDLIB_PHONE_NUMBER -e TDLIB_AUTH_CODE -e TDLIB_2FA_PASSWORD -e MCP_READ_ONLY -e MCP_TOOL_PROFILE ghcr.io/tolboy/telegram-mcp-tdlib:1.17.0-stdio. It reads these environment variables: TDLIB_API_ID (required), TDLIB_API_HASH (required, secret), TDLIB_PHONE_NUMBER (secret), TDLIB_AUTH_CODE (secret), TDLIB_2FA_PASSWORD (secret), MCP_READ_ONLY and MCP_TOOL_PROFILE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"telegram-mcp-tdlib": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TDLIB_API_ID",
"-e",
"TDLIB_API_HASH",
"-e",
"TDLIB_PHONE_NUMBER",
"-e",
"TDLIB_AUTH_CODE",
"-e",
"TDLIB_2FA_PASSWORD",
"-e",
"MCP_READ_ONLY",
"-e",
"MCP_TOOL_PROFILE",
"ghcr.io/tolboy/telegram-mcp-tdlib:1.17.0-stdio"
],
"env": {
"TDLIB_API_ID": "<value>",
"TDLIB_API_HASH": "<secret>",
"TDLIB_PHONE_NUMBER": "<secret>",
"TDLIB_AUTH_CODE": "<secret>",
"TDLIB_2FA_PASSWORD": "<secret>",
"MCP_READ_ONLY": "<value>",
"MCP_TOOL_PROFILE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| TelbaseDeploy any web project with one command. AI-native platform with self-healing feedback. | Local · stdio |
| Telegram Archive MCPMCP server for Telegram Archive — search messages, browse chats, and access history. | Local · stdio |
| Telegram MCPTelegram MCP server: read, send, and search messages and manage chats via your account. | Local · stdio |
| Telegram MCPTelegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack. | Remote · HTTP |
| TeleKashOracle MCP-SERVERPrediction market probability oracle. 500+ markets from Kalshi, Polymarket & Metaculus. | Local · stdio |
| telescopecomparehq.comTelescopeCompareHQ: the site's own MCP server — dataset, enquiry (enquiry = a human handoff, not... | Remote · HTTP |
| Telethon PlusSelf-hosted MCP server: Telegram userbot control (Telethon) via HTTP and MCP. | Local · HTTP |
| telleroutlook MCP-SERVERWasmAgent MCP server — WASM-sandboxed code execution with capability manifests and Tasks API. | Local · stdio |