Telegram MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOT_TOKEN | Yes | The Telegram bot token from @BotFather (`/newbot`). Every key (token signing, webhook secret) is derived from it, so revoking the token invalidates all sessions and links. | |
| RETENTION_DAYS | No | How many days the bot stores what Telegram delivers to it before deleting the rest. | 14 |
| ALLOWED_USER_IDS | No | Optional comma-separated list of Telegram user IDs allowed to connect. By default anyone may connect their own Telegram account to the deployment; when set, others get "this bot is private" and groups added by someone not on the list are left at once. | |
| DEV_SKIP_IP_CHECK | No | Set to 1 (in `.dev.vars` or `.env`) so local dev can feed the Worker webhook calls from your machine. Never set in production. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed