Telegram MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_MCP_CONFIG | No | Override the default config file path. Defaults to ~/.config/telegram-mcp-v2/config.json (or %APPDATA%\telegram-mcp-v2\config.json on Windows). | |
| TELEGRAM_MCP_CACHE_KEY | No | Encryption key for the encrypted SQLite cache. Required when the encrypted-cache option is enabled. | |
| TELEGRAM_MCP_CONFIG_DIR | No | Override the default config directory. Alternative to TELEGRAM_MCP_CONFIG. | |
| TELEGRAM_MCP_MASTER_KEY | No | Master key for encrypted session storage fallback when no OS keyring is available. Must be set before login and before starting the MCP server. | |
| TELEGRAM_MCP_UPLOAD_DIR | No | Directory for media uploads. Required to use media upload tools; arbitrary filesystem paths are rejected. | |
| TELEGRAM_MCP_DOWNLOAD_DIR | No | Directory for downloads. Defaults to the private application config directory if not set. |
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 |
|---|---|
| inspect_permissionsA | Show the active profile, allowed capabilities, and physically exposed tools. |
| telegram_diagnosticsA | Inspect local runtime/config/storage state without returning secrets or messages. |
| list_chat_foldersC | List Telegram chat folders without changing their configuration. |
| list_folder_chatsC | List chats visible in one Telegram folder by its numeric folder id. |
| list_chatsC | List chats, stable references, unread counts, and pinned state. |
| list_forum_topicsC | List topics in a Telegram forum chat, including unread state. |
| read_forum_topicB | Read recent messages from one forum topic without marking it read. |
| read_chatC | Read recent messages from a chat, returned oldest-first. |
| get_unreadA | Return unread messages grouped by chat without marking them read. |
| get_message_contextC | Read one message and bounded surrounding context. |
| search_chatC | Search message text within one chat. |
| search_globalC | Search message text across all dialogs. |
| search_forum_topicC | Search message text inside one forum topic. |
| analyze_chat_activityC | Compute deterministic activity statistics; the calling agent writes narrative analysis. |
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 14 tools
Each tool targets a distinct scope or operation: search by chat/global/forum topic, list chats/folders/topics, read chat/topic/unread/context, plus analysis and diagnostics. Overlaps are minimal and descriptions clearly differentiate boundaries (e.g., read_chat vs read_forum_topic).
Most tools follow a consistent verb_noun snake_case pattern (search_chat, list_chats, get_unread). One outlier is telegram_diagnostics, which lacks a verb and slightly breaks the pattern, but overall naming is predictable.
14 tools is well-scoped for a read-only Telegram client surface, covering search, read, list, and diagnostic needs without redundant or excessive operations.
The read-only surface is quite complete for searching, reading, listing, and analyzing chats, including unread and forum topic support. Minor gaps remain in exposing detailed chat metadata (e.g., profile info) or any write operations, though the latter may be intentional.