Telegram MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port MCP-сервера (default 3200) | 3200 |
| API_KEY | Yes | Ключ доступа — клиенты передают в X-API-Key или Authorization: Bearer <key> | |
| TG_API_ID | Yes | api_id с my.telegram.org | |
| TG_CHANNEL | No | Канал по умолчанию: @username, t.me/... или -100<id> (опционален, если передан в инструменте) | |
| TG_SESSION | Yes | Строка сессии из npm run login | |
| TG_API_HASH | Yes | api_hash с my.telegram.org | |
| TG_FLOOD_SLEEP_THRESHOLD | No | Секунд: автоматически пересиживать FLOOD_WAIT короче этого значения (default 60) | 60 |
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
Maintenance
ActivitySlowing
ResponsivenessNo issues