Telegram MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_BOT_TOKEN | Yes | Your Telegram bot token from @BotFather, set in config.env |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageA | Send a text message through the Telegram bot. Text over 4096 characters is split into several messages. |
| send_photoA | Send a photo through the Telegram bot from an absolute local path (.jpg, .jpeg, .png, .webp, up to 10 MB) or an http(s) URL. |
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 2 tools
The two tools have clearly distinct purposes: one sends text, the other sends an image from a path or URL. There is no realistic chance of an agent selecting the wrong tool for a given request.
Both tools follow the same verb_noun snake_case convention (send_message, send_photo) and are intuitively named. No mixed conventions or vague verbs.
Two tools is very thin for a server billed as a general Telegram integration. It is not wrong for a minimal outbound bot, but it sits at the borderline of a usable surface.
Outbound text and photo sending are covered, but there is no way to read incoming messages, edit or delete sent messages, or send other media such as documents, audio, or video. These are notable gaps for a Telegram messaging server that agents may stumble on.