Telegram MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_PHONE | Yes | Your phone number with country code (e.g., +1234567890) | |
| TELEGRAM_API_ID | Yes | Your Telegram API ID from my.telegram.org | |
| TELEGRAM_API_HASH | Yes | Your Telegram API hash from my.telegram.org |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chatsA | List all chats, groups, and channels you have access to |
| get_chat_infoB | Get detailed information about a specific chat |
| search_chatsB | Search for chats by title or username |
| get_messagesA | Get recent messages from a specific chat. Use "me" as chatId for your own Saved Messages. |
| send_messageA | Send a text message to a chat |
| search_messagesA | Search for messages across all chats or within a specific chat |
| mark_as_readB | Mark specific messages as read in a chat |
| get_user_infoB | Get information about a specific user |
| get_media_contentC | Download media content from a message |
| send_mediaC | Send media file to a chat |
| get_media_infoC | Get information about media in a message |
| edit_messageC | Edit an existing message |
| delete_messageC | Delete a message |
| forward_messageC | Forward a message to another chat |
| get_message_contextC | Get detailed context for a message including reply chain and thread |
| send_documentC | Send a document file to a chat |
| download_fileC | Download a file from a message |
| get_file_infoC | Get detailed information about a file in a message |
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 18 tools
Multiple tools have unclear boundaries, particularly around files/media: get_file_info vs get_media_info, get_media_content vs download_file, and send_media vs send_document are easily confused. The descriptions do not clearly differentiate these tools, which could lead an agent to select the wrong one.
All tool names follow a consistent verb_noun snake_case pattern (e.g., search_chats, send_message, get_chat_info). This makes the naming predictable and easy to learn, with no mixed styles or arbitrary deviations.
The server has 18 tools, slightly above the typical well-scoped range of 3-15. However, given the breadth of Telegram's API and the need to cover messaging, media, search, and chat management, the count is reasonable and not excessive.
The tool set covers the core Telegram operations: sending messages/media, retrieving messages, searching, editing/deleting/forwarding, and chat/user info. Minor gaps exist, such as no direct 'get message by ID' or chat management operations like leaving a chat, but agents can generally accomplish tasks with the provided tools.