Telegram Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for the streamable HTTP server (default: 3099) | |
| TTS_HOST | No | OpenAI-compatible TTS endpoint URL | |
| BOT_TOKEN | Yes | Your Telegram bot token from @BotFather | |
| TTS_VOICE | No | Voice for TTS (e.g., af_heart) | |
| TTS_FORMAT | No | Audio format for TTS (e.g., ogg, mp3) | |
| WHISPER_MODEL | No | Whisper model name (default: onnx-community/whisper-base) | |
| OPENAI_API_KEY | No | OpenAI API key for TTS via OpenAI | |
| ALLOWED_USER_ID | Yes | Your Telegram user ID (numeric) | |
| WHISPER_CACHE_DIR | No | Cache directory for Whisper model |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| helpA | Discovery for this MCP server. No args -> overview. topic: 'index' -> topic menu. topic: 'guide' -> comms guide. topic: '<tool/topic>' -> detailed help. |
| dequeueA | Consume queued updates. Non-content events drain first, then up to one content event (text, media, voice) is appended. Returns: |
| sendA | Send a message as text, audio (TTS), or both. text only → text message with auto-split and Markdown. audio only → TTS voice note (spoken content). Both → voice note with text as caption (keep brief — topic context before playback). At least one of text or audio is required. For structured status, use notify. For file attachments, use send_file. For interactive prompts, use ask, choose, or confirm. Pass type: "" to route to a specific mode. Call with no args to see available types. |
| actionA | Universal action dispatcher. Omit |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| agent-guide | Agent behavior guide for this MCP server. Read this at session start to understand how to communicate with the user and which tools to use. |
| communication-guide | Compact Telegram communication patterns: tool selection, hard rules, commit/push flow, multi-step tasks, and loop behavior. |
| quick-reference | Hard rules + tool selection table for Telegram communication. Minimal injected rules card — full detail in communication-guide. |
| setup-guide | Step-by-step guide to creating a Telegram bot and running pnpm pair to configure this MCP server. |
| formatting-guide | Reference for Markdown/HTML/MarkdownV2 formatting in Telegram messages. Consult this when unsure how to format text. |
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