Telegram Pager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_API_ID | Yes | Your Telegram API ID from my.telegram.org | |
| TELEGRAM_SESSION | Yes | Your Telegram session string generated by the authentication script | |
| TELEGRAM_API_HASH | Yes | Your Telegram API hash from my.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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_telegram_messageB | Send a direct message to a Telegram user. Do not use the @ symbol in the username (e.g. use 'jakethesnake', not '@jakethesnake'). |
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 confusion between tools.
The single tool uses a clear verb_noun pattern (send_telegram_message), which is consistent and predictable.
One tool is borderline for the 'Telegram Pager' purpose; while it could be sufficient for a narrowly scoped paging server, it feels thin compared to typical server sizes.
The server only supports sending messages, lacking any other operations like checking delivery status or managing contacts, which are significant gaps for a Telegram integration.