docker-telethon-plus
by psyb0t
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELETHON_API_ID | Yes | API ID from my.telegram.org | |
| TELETHON_DRY_RUN | No | If true, write endpoints validate but don't call Telegram | false |
| TELETHON_SESSION | Yes | StringSession from the login helper | |
| TELETHON_API_HASH | Yes | API hash from my.telegram.org | |
| TELETHON_AUTH_KEY | No | When set, all endpoints require Authorization: Bearer <key> | |
| TELETHON_LOG_LEVEL | No | DEBUG, INFO, WARNING, ERROR | INFO |
| TELETHON_READ_ONLY | No | If true, all write endpoints return 403 | false |
| TELETHON_CACHE_PATH | No | Path to the entity cache file | /cache/entities.json |
| TELETHON_APP_VERSION | No | What Telegram thinks your app is | 1.0 |
| TELETHON_POST_TO_URL | No | URL to POST incoming update events to | |
| TELETHON_DEVICE_MODEL | No | What Telegram thinks your device is | docker-telethon-plus |
| TELETHON_DOWNLOAD_DIR | No | Scratch space for send_file uploads | /tmp/telethon-plus |
| TELETHON_CACHE_ENABLED | No | Persist resolved entities to disk | true |
| TELETHON_SYSTEM_VERSION | No | What Telegram thinks your OS is | 1.0 |
| TELETHON_REQUEST_TIMEOUT | No | Per-request timeout in seconds | 60 |
| TELETHON_THROTTLE_ENABLED | No | Master switch for all rate-limiting | true |
| TELETHON_CACHE_TTL_SECONDS | No | TTL for cached entities in seconds | 604800 |
| TELETHON_THROTTLE_ADAPTIVE | No | On each FLOOD_WAIT, multiply all waits ×2 for an hour | true |
| TELETHON_THROTTLE_JITTER_MS | No | Random ±jitter added on top | 200 |
| TELETHON_BUCKET_READ_PER_MIN | No | Cap on read ops | 600 |
| TELETHON_BUCKET_SEND_PER_MIN | No | Cap on sends across all chats | 20 |
| TELETHON_HTTP_LISTEN_ADDRESS | No | host:port to bind | 0.0.0.0:8080 |
| TELETHON_UPDATES_BUFFER_SIZE | No | Buffer size for slow WebSocket consumers | |
| TELETHON_BUCKET_JOIN_PER_HOUR | No | Cap on channel/group joins | 5 |
| TELETHON_FLOOD_SLEEP_THRESHOLD | No | Auto-sleep through FLOOD_WAIT errors below this many seconds | 60 |
| TELETHON_BUCKET_CREATE_PER_HOUR | No | Cap on channel/group creation | 5 |
| TELETHON_BUCKET_RESOLVE_PER_MIN | No | Cap on resolveUsername | 5 |
| TELETHON_BUCKET_GET_FULL_PER_MIN | No | Cap on getFullChannel / getFullUser / get_participants | 10 |
| TELETHON_THROTTLE_GLOBAL_INTERVAL_MS | No | Min gap between any two outgoing requests | 50 |
| TELETHON_THROTTLE_PER_CHAT_INTERVAL_MS | No | Min gap between sends to the same chat | 1100 |
| TELETHON_THROTTLE_PER_CHAT_READ_INTERVAL_MS | No | Min gap between reads from the same chat | 250 |
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/psyb0t/docker-telethon-plus'
If you have feedback or need assistance with the MCP directory API, please join our Discord server