mcp-telegram-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOT_TELEGRAM_ID | No | Alias for BOT_TELEGRAM_CHAT_ID | |
| BOT_TELEGRAM_URL | No | Full sendMessage URL (legacy fallback, replaces token and chat_id) | |
| BOT_TELEGRAM_TOKEN | No | Telegram bot token (required unless using BOT_TELEGRAM_URL) | |
| BOT_TELEGRAM_CHAT_ID | No | Telegram chat ID | |
| BOT_TELEGRAM_THREAD_ID | No | Thread ID for forum topics | |
| BOT_TELEGRAM_TIMEOUT_MS | No | Timeout in milliseconds | 10000 |
| BOT_TELEGRAM_API_BASE_URL | No | API base URL | https://api.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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| telegram_onboarding_prepareC | Prepare onboarding instructions to link a Telegram bot and auto-generate MCP config. |
| telegram_onboarding_verifyB | Verify setup code in Telegram updates, require explicit chat_id confirmation, generate ready MCP config, and optionally send a test message. |
| send_telegram_notificationA | Send a notification to the configured Telegram chat. Supports: plain text, photo, audio, or document — with an optional caption. You can send text only, media only, or media + caption together. For media: provide a media object with type and either a public url or base64Data. |
| telegram_config_statusA | Check whether Telegram configuration is valid for this MCP server. |
| telegram_send_and_wait_replyA | Send a message to Telegram and block until a reply arrives in the same chat. Supports: plain text, photo, audio, or document — with an optional caption. You can send text only, media only, or media + caption together. For media: provide a media object with type and either a public url or base64Data. Sends an instant ACK back to Telegram when a reply is received. Returns reply text + ack_message_id so you can later edit the ACK with your final response. |
| telegram_edit_messageA | Edit a previously sent Telegram message by its message_id. Use to replace the ACK with a final response. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| agent-install-and-onboard | Operational protocol for agents to install, activate, and execute secure onboarding with chat_id confirmation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The two sending tools (send_telegram_notification and telegram_send_and_wait_reply) overlap in message types and could be confused, though the blocking/waiting behavior distinguishes them. Other tools are clearly distinct.
Most tools follow a 'telegram_' prefix convention, but send_telegram_notification breaks the pattern by placing 'telegram' at the end. Additionally, telegram_config_status is a noun phrase rather than a verb, mixing command and state check styles.
With 6 tools, the set is well-scoped for a Telegram agent, covering onboarding, sending, waiting for replies, and editing messages without unnecessary redundancy.
The main workflow is supported: onboarding verification, sending messages, and replying via edit. A notable gap is the lack of a tool to handle incoming Telegram updates initiated by the user, but the core lifecycle is covered.