Telegram MCP server (MTProto). Connect Claude, Cursor, Claude Code, VS Code, Codex, Cline, Windsurf to a real Telegram account — read/search/send
Telegram MCP server (MTProto). Connect Claude, Cursor, Claude Code, VS Code, Codex, Cline, Windsurf to a real Telegram account — read/search/send messages, moderate channels, manage stories/contacts/folders, transcribe voice, and call any. Exposed over MCP by the mcp telegram mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Telegram MCP server for Claude, Codex, Cursor, Claude Code, VS Code, Cline, Windsurf, and other MCP clients. Real Telegram user account via MTProto, browser-based local sign-in, 100+ tools. Need lazy-loading + lower context cost? See telegram-agent, the skill-based companion.
Everything the assistant can do here goes through one of these:
login — Open the browser-based sign-in flow. Adds an accountlist_accounts — List signed-in accountslist_dialogs — List dialogs/chats/channels. Filters: unread, archived, ignorePinned, folder, limitlist_messages — List messages in a dialog. Newest firstsearch_messages — Search inside one dialog: query, filter (photos/videos/url/voice/...), fromUser, date rangesearch_global — Search across every chat you havesearch_dialogs — Find dialogs by name/title/username substringsend_message — Send text. Supports replyTo, topMsgId, parseMode, schedule, silentsend_file — Send a file (local path or https:// URL). Pass an array for an albumdownload_media — Save the media on a message to disktranscribe_message — Transcribe a voice/video note (Premium)invoke_mtproto — Call any raw MTProto method by name. Auto-resolves peer/channel/user stringsBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: TELEGRAM_API_ID, TELEGRAM_API_HASH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
>=20 2. Telegram API credentials from my.telegram.org/apps — api_id and api_hashAmong the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Telegram's toolset — login, list_accounts, list_dialogs and 11 more — is a fair guide to whether it matches your workflow. It is maintained by tacticlaunch; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Telegram's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| login | Open the browser-based sign-in flow. Adds an account. |
| list_accounts | List signed-in accounts. |
| list_dialogs | List dialogs/chats/channels. Filters: unread, archived, ignorePinned, folder, limit. |
| list_messages | List messages in a dialog. Newest first. |
| search_messages | Search inside one dialog: query, filter (photos/videos/url/voice/...), fromUser, date range. |
| search_global | Search across every chat you have. |
| search_dialogs | Find dialogs by name/title/username substring. |
| send_message | Send text. Supports replyTo, topMsgId, parseMode, schedule, silent. |
| send_file | Send a file (local path or https:// URL). Pass an array for an album. |
| download_media | Save the media on a message to disk. |
| transcribe_message | Transcribe a voice/video note (Premium). |
| invoke_mtproto | Call any raw MTProto method by name. Auto-resolves peer/channel/user strings. |
| logout | Drop a local session and revoke it on Telegram. |
| open_settings | Open the local settings page (tool surface + read-only). |
{
"mcpServers": {
"telegram-tacticlaunch": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"TELEGRAM_API_ID": "your-value",
"TELEGRAM_API_HASH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
>=20 2. Telegram API credentials from my.telegram.org/apps — api_id and api_hash| Variable | Description | Required |
|---|---|---|
| TELEGRAM_API_ID | Configuration value read at startup. | Optional |
| TELEGRAM_API_HASH | Configuration value read at startup. | Optional |
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.