telegram-call-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | stderr logging verbosity. | INFO |
| TTS_MODEL | No | Any TTS model on OpenRouter's /audio/speech endpoint. | fish-audio/s1 |
| TTS_VOICE | No | Voice name, if the model supports it. | |
| TTS_BASE_URL | No | Any OpenAI-compatible audio API works. | https://openrouter.ai/api/v1 |
| TELEGRAM_PROXY | No | socks5://host:port or http://host:port for MTProto (Telethon ignores HTTP_PROXY). | |
| TELEGRAM_API_ID | Yes | API ID from my.telegram.org (required). | |
| CALL_REPEAT_PAUSE | No | Pause between repeats, seconds. | 2 |
| TELEGRAM_API_HASH | Yes | API hash from my.telegram.org (required). | |
| MAX_MESSAGE_LENGTH | No | Message length cap after sanitization. | 500 |
| OPENROUTER_API_KEY | Yes | OpenRouter API key for TTS (required). | |
| CALL_ANSWER_TIMEOUT | No | Seconds to wait for the callee to answer. | 45 |
| CALL_TARGET_USER_ID | Yes | Numeric Telegram user ID to call (required). | |
| TELEGRAM_SESSION_PATH | No | Session file location (without .session). | ~/.telegram-call-mcp/telegram |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| make_callA | Place a real Telegram voice call to the owner and speak the message aloud. Use this when something is urgent enough to interrupt the owner with a
ringing phone call — a critical incident, a failed deployment, anything
they asked to be actively alerted about. The call rings like a normal
Telegram call; once answered, the synthesized message plays |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/maloleg/telegram-call-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server