Telegram Notify MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_USERNAME | Yes | Your Telegram username (without the @) | |
| 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageB | Send a text message to the configured Telegram user |
| send_photoA | Send a photo to the configured Telegram user. Accepts a URL or local file path. |
| send_documentB | Send a document or file to the configured Telegram user. Accepts a URL or local file path. |
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 3 tools
Each tool targets a distinct content type: text, photo, or document. There is no overlap in purpose, making them easily distinguishable.
All tool names follow a consistent 'send_' prefix followed by the content type (message, photo, document), forming a clear and predictable pattern.
Three tools cover the essential notification actions (text, photo, document) without unnecessary extras, perfectly scoped for a notification server.
The set covers the most common message types. Minor gaps like video or audio are absent, but for a basic notify server this is not a significant omission.