Claude Code Telegram Notifier MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADMIN_ID | Yes | Your numeric Telegram User ID, obtained from @userinfobot or @rawdatabot (e.g. 987654321). | |
| BOT_TOKEN | Yes | Your Telegram Bot API token obtained from @BotFather (e.g. 123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ). |
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_updateA | Send a vital update, progress log, or status notification to the user's Telegram. Use this when starting a long task, when reaching significant milestones, or when you encounter a blocker/need the user to return to the computer to approve an action. |
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
With only a single tool, there is no possibility of confusion or misselection between tools. The tool's purpose is self-evident and unambiguous.
The lone name send_telegram_update follows a clear verb_noun snake_case convention. With one tool there is no inconsistency to speak of.
A single tool is borderline thin for a server, though the notifier's scope is narrow. One send operation arguably covers the entire purpose, but it leaves little room for nuance.
Sending a notification is the only real operation for a notifier, so the surface covers the domain's core action. Minor gaps exist (e.g. no distinct channels for errors vs. progress), but the stated use cases are handled.