Telegram MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment (production/development) | |
| TELEGRAM_BOT_TOKEN | Yes | Your Telegram bot token from @BotFather | |
| TELEGRAM_CHANNEL_ID | Yes | Target channel ID (e.g., @mychannel) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageC | Send a text message to the Telegram channel |
| send_photoC | Send a photo to the Telegram channel |
| send_pollC | Create and send a poll to the Telegram channel |
| send_reactionC | Send a reaction to a message |
| edit_messageC | Edit an existing message |
| delete_messageC | Delete a message from the channel |
| get_channel_infoB | Get information about the Telegram channel |
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 7 tools
Each tool has a clearly distinct purpose targeting specific actions in the Telegram domain. For example, send_message, send_photo, and send_poll handle different content types, while delete_message, edit_message, and send_reaction operate on existing messages with unique functions. No tools appear to overlap or cause confusion.
All tool names follow a consistent verb_noun pattern using snake_case, such as delete_message, edit_message, and send_photo. This predictable naming convention makes it easy for agents to understand and select the appropriate tool without ambiguity.
With 7 tools, this server is well-scoped for managing a Telegram channel, covering essential operations like sending various content types, editing, deleting, and reacting to messages. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides strong coverage for core Telegram channel interactions, including sending, editing, deleting, and reacting to messages. A minor gap exists in operations like retrieving message history or handling other media types (e.g., videos or documents), but agents can work around this with the available tools.