MCP Telegram
by overpod
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_USE_WSS | No | Set to 'true' to use port 443 instead of 80 (default: false) | |
| TELEGRAM_API_HASH | Yes | Your Telegram API hash from my.telegram.org | |
| TELEGRAM_PROXY_IP | No | Proxy server address (optional) | |
| MCP_TELEGRAM_DAEMON | No | Set to '1' to run in daemon mode (optional) | |
| TELEGRAM_PROXY_PORT | No | Proxy server port (optional) | |
| TELEGRAM_PROXY_SECRET | No | MTProxy secret (enables MTProxy mode) | |
| TELEGRAM_SESSION_PATH | No | Path to store the session file (default: ~/.mcp-telegram/session) | |
| TELEGRAM_PROXY_PASSWORD | No | Optional proxy auth password | |
| TELEGRAM_PROXY_USERNAME | No | Optional proxy auth username | |
| MCP_TELEGRAM_ENABLE_STARS | No | Set to '1' to enable stars tools | |
| TELEGRAM_PROXY_SOCKS_TYPE | No | SOCKS type: 4 or 5 (default: 5) | |
| MCP_TELEGRAM_ENABLE_GROUP_CALLS | No | Set to '1' to enable group call tools | |
| MCP_TELEGRAM_ENABLE_QUICK_REPLIES | No | Set to '1' to enable quick replies tools |
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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/overpod/mcp-telegram'
If you have feedback or need assistance with the MCP directory API, please join our Discord server