Telegram Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOT_TOKEN | Yes | The token provided by @BotFather for your Telegram bot. | |
| WHISPER_MODEL | No | The Whisper model to use for local voice transcription. | onnx-community/whisper-base |
| ALLOWED_CHAT_ID | Yes | The chat ID where outbound messages are restricted to. Outbound tool calls to any other chat are rejected. | |
| ALLOWED_USER_ID | Yes | The user ID allowed to interact with the bot. Inbound updates from any other user are silently discarded. | |
| WHISPER_CACHE_DIR | No | Optional directory where Whisper model weights are cached. |
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/electricessence/Telegram-Bridge-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server