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`). Required for deployment. Every key (token signing, webhook secret) is derived from this token; revoking it in BotFather invalidates all sessions and links. | |
| RETENTION_DAYS | No | Number of days stored messages are kept before being deleted (default 14). Increasing it costs D1 storage, not writes. Memory is not limited by this. | |
| ALLOWED_USER_IDS | No | Optional comma-separated list of Telegram user IDs allowed to connect their account to this deployment. When empty, anyone may connect their own Telegram account (and add the bot to groups), so setting it locks the bot to specific people. | |
| DEV_SKIP_IP_CHECK | No | Set to 1 in `.dev.vars`/`.env` when running `bun run dev` to skip the webhook IP check and feed webhook calls from your machine. Never set this 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 | |