Telegram MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_API_ID | Yes | Your Telegram API ID from https://my.telegram.org | |
| TELEGRAM_API_HASH | Yes | Your Telegram API hash from https://my.telegram.org | |
| TELEGRAM_SESSION_PATH | No | Path to the Telegram user session file (created by telegram-mcp-login) | |
| TELEGRAM_ALLOWED_CHAT_IDS | No | Comma-separated list of allowed chat IDs. Empty means all ordinary cloud chats are accessible. | |
| TELEGRAM_MAX_SEARCH_RESULTS | No | Maximum number of search results (default: 100) | 100 |
| TELEGRAM_MAX_MESSAGES_PER_REQUEST | No | Maximum number of messages per request (default: 100) | 100 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| telegram_list_chatsB | List Telegram cloud chats allowed by the local access policy. |
| telegram_get_messagesA | Read messages from one allowed chat, newest first, without marking them read. |
| telegram_search_messagesC | Search text globally or inside one allowed Telegram chat. |
| telegram_get_message_contextC | Read a target message together with nearby messages in chronological order. |
| telegram_get_chat_infoB | Return basic metadata for one allowed chat. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: listing chats, getting chat info, retrieving messages, getting message context with surrounding messages, and searching. No overlap in functionality.
All tools follow the consistent pattern 'telegram_verb_noun', with verbs like get, list, search used predictably.
5 tools is appropriate for a focused read-only Telegram bridge, covering core operations without being excessive or insufficient.
The tool set covers reading and searching but lacks send, delete, or chat management operations, which are notable gaps for a Telegram bridge if write capabilities are expected.