telegram-mcp
by t0uchY233
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3000 |
| LOG_LEVEL | No | Pino log level: trace|debug|info|warn|error | info |
| TELEGRAM_MOCK | No | Set true to use mock data (no real Telegram needed) | |
| TELEGRAM_API_ID | No | From my.telegram.org | |
| TELEGRAM_SESSION | No | Generated by browser auth or `bun run auth` | |
| TELEGRAM_API_HASH | No | From my.telegram.org | |
| TELEGRAM_MCP_CONFIG | No | Write-tool allowlist path | bot-data/config.yml |
| KEEPALIVE_INTERVAL_MS | No | Session keepalive interval in ms (default 6 hours) | 21600000 |
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
- 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/t0uchY233/telegram-summarize'
If you have feedback or need assistance with the MCP directory API, please join our Discord server