mcp-telegram-claudecode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PROXY | No | HTTP proxy URL (e.g., http://127.0.0.1:7890) | |
| HTTPS_PROXY | No | HTTPS proxy URL (alternative to HTTP_PROXY) | |
| TELEGRAM_CHAT_ID | Yes | Your chat ID from @userinfobot | |
| TELEGRAM_BOT_TOKEN | Yes | 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| telegram_send_messageA | Send a text message to the configured Telegram chat. IMPORTANT: You MUST use this tool to reply to the user regardless of whether they sent their message via terminal or Telegram. Always respond through Telegram so the user can see your replies on their phone. |
| telegram_get_messagesA | Get recent messages from Telegram. Use this to check for new messages from the user. |
| telegram_check_newA | Quick check if there are new messages from Telegram without retrieving all of them. |
| telegram_send_photoB | Send a photo/image to the configured Telegram chat. |
| telegram_send_videoA | Send a video file to the configured Telegram chat. Supports mp4, mov, avi and other video formats. Max file size: 50MB. |
| telegram_send_documentA | Send any file/document to the configured Telegram chat. Use this for files that are not photos or videos (e.g., zip, pdf, txt, etc.). Max file size: 50MB. |
| telegram_start_pollingA | Manually start auto-polling for Telegram messages (polling starts automatically on MCP load, so this is usually not needed). When enabled, new messages will be automatically injected into the terminal as user input. |
| telegram_stop_pollingA | Stop auto-polling for Telegram messages. |
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 8 tools
The tools are mostly distinct: send_message, send_photo, send_video, and send_document are clearly separated by content type, and start/stop_polling are unique. However, get_messages and check_new could cause slight confusion, as both relate to retrieving new messages, though their descriptions differentiate by urgency and scope.
All tools follow a consistent telegram_ + verb_noun pattern (send_message, get_messages, send_photo, start_polling). The only slight deviation is telegram_check_new, where 'new' is an adjective rather than a noun, but it remains understandable and consistent with the overall style.
With 8 tools, the server is well-scoped for its purpose: messaging, media sending, message retrieval, and polling control. Each tool serves a distinct function without redundancy.
The tool set covers the core Telegram operations needed for a Claude Code integration: sending text, photos, videos, documents, retrieving messages, and managing polling. Missing features like editing or deleting messages are not critical for this use case.