Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Telegram's MCP servers take an unusual route: instead of a bot API (which can't read arbitrary chats), the leading implementations use Telegram's client API via MTProto — the assistant effectively acts as your own Telegram account, seeing what you see. That makes them far more capable than a typical bot bridge, and correspondingly more sensitive.
With it configured, your assistant can list your dialogs, read history from chats, groups and channels you're in, and send messages as you. The value concentrates in triage and digestion: Telegram power users accumulate dozens of channels and group chats, and "summarise what mattered across my feeds this morning" is exactly the kind of task an assistant does better than a thumb-scrolling human. Extracting action items from a chaotic group planning thread, catching up a muted channel, drafting replies in your voice for approval — all natural fits.
Setup reflects the client-API approach: you register an application at my.telegram.org to get an api_id and api_hash, then complete a one-time login (phone code, plus 2FA password if set) to produce a session the server reuses. Implementations vary — chigwell/telegram-mcp (Python, Telethon) is a full-featured choice with dozens of tools; chaindead's Go implementation focuses on a tighter dialogs/read/send core.
Be clear-eyed about the trust model: the session string is a key to your entire Telegram account, so store it like a password, and let the client's tool-confirmation flow gate anything that sends. Used with that care, it turns Telegram from an attention sink into something you consult on your terms.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Dozens of channels condensed into one 'what actually mattered' briefing.
Action items and decisions extracted from sprawling planning threads.
Responses drafted in your voice, sent only after you approve.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| get_chats | List your dialogs (chats, groups, channels) with pagination |
| list_messages | Read message history from a chat with filters |
| send_message | Send a message to a chat as your account |
| get_contacts | List contacts |
| search_public_chats | Search public channels and groups |
| get_me | Your own account info |
{
"mcpServers": {
"telegram-mcp": {
"command": "uv",
"args": [
"--directory",
"/full/path/to/telegram-mcp",
"run",
"main.py"
],
"env": {
"TELEGRAM_API_ID": "your_api_id_here",
"TELEGRAM_API_HASH": "your_api_hash_here",
"TELEGRAM_SESSION_STRING": "your_session_string_here"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Telegram API credentials from my.telegram.org and a one-time login to generate a session string. Python with uv.
| Variable | Description | Required |
|---|---|---|
| TELEGRAM_API_ID | Declared in the maintainer’s client configuration. | Check documentation |
| TELEGRAM_API_HASH | Declared in the maintainer’s client configuration. | Check documentation |
| TELEGRAM_SESSION_STRING | Declared in the maintainer’s client configuration. | Check documentation |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).
A server that provides a Model Context Protocol (MCP) interface to interact with WhatsApp Business API using FastMCP.
Detect what changed on a page, sitemap or feed since the last check, with a diff and email alert
Find opportunities, track market activity, and discover business signals with real-time data.