Telegram MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEB_PORT | No | Web interface port (default: 3000) | 3000 |
| TELEGRAM_BOT_TOKEN | Yes | Your bot token from @BotFather | |
| TELEGRAM_DEFAULT_USER | No | Default chat ID or username for messages |
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 |
|---|---|
| send_telegram_messageB | Send a message to the default Telegram user configured in .env file. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly stated.
The tool name follows a clear verb_noun pattern (send_telegram_message), and with only one tool, consistency is trivially maintained.
A single tool is far too few for a Telegram MCP server, which typically requires sending, receiving, editing, and media operations. The narrow scope of sending only to a default user makes the server feel like a minimal notification service rather than a general Telegram integration.
The tool surface is severely incomplete, covering only text message sending to a default recipient. Missing common operations such as sending media, editing messages, handling updates, and selecting recipients makes most Telegram workflows impossible.