claude-telegram-interactive-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | HTTP proxy URL | |
| HTTPS_PROXY | No | HTTPS proxy URL | |
| TELEGRAM_CHAT_ID | Yes | Numeric Telegram chat ID | |
| TELEGRAM_BOT_TOKEN | Yes | Telegram bot token from BotFather |
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_markdown_message_as_telegram_botB | Send a message using Telegram bot in HTML or Markdown format (default: HTML) |
| send_telegram_documentB | Send a document/file via Telegram bot (supports local Windows paths and HTTP URLs) |
| send_telegram_photoA | Send a photo/image via Telegram bot (supports local Windows paths and HTTP URLs) |
| send_telegram_videoA | Send a video via Telegram bot (supports local Windows paths and HTTP URLs) |
| ask_telegram_confirmationA | Send a question with interactive inline buttons and/or wait for user text or attached file/photo/mediagroup response. Automatically downloads received files to disk and returns their local paths. |
| fetch_telegram_updatesA | Poll and retrieve recent messages, photos, error screenshots, files, and mediagroups sent to the bot. Automatically downloads all media to local disk and returns paths. |
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 6 tools
Each tool has a distinct purpose: sending different media types, sending text, asking for interactive input, and fetching updates. No overlapping functionality causes confusion; the boundaries are clear.
All tools use snake_case with a verb-first pattern (send_*, ask_*, fetch_*). Even the longer 'send_markdown_message_as_telegram_bot' follows the same convention, making the set predictable and easy to scan.
With 6 tools, the server is well-scoped for Telegram bot interaction. Each tool covers a core operation without redundancy, and the count is neither sparse nor overwhelming.
The set covers sending text, documents, photos, videos, interactive confirmations, and fetching updates. It lacks some capabilities like editing messages or sending audio, but the core lifecycle of sending and receiving is fully covered.