telegram-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APP_PORT | No | Host port on 127.0.0.1 (Compose only). | 3440 |
| MCP_TOKENS | Yes | Comma-separated MCP tokens; /mcp answers 401 without one, and 503 if none is set. | |
| PUBLIC_HOST | Yes | The public host name, for the DNS-rebinding check. | |
| RATE_PER_DAY | No | Sends per MCP token per day; each message part or file counts. | 1000 |
| MAX_UPLOAD_MB | No | Largest data: URL or base64 file the server forwards. | 15 |
| RATE_PER_MINUTE | No | Sends per MCP token per minute; each message part or file counts. | 30 |
| TELEGRAM_API_BASE | No | For tests or a local Bot API server. | https://api.telegram.org |
| TELEGRAM_MCP_IMAGE | No | The image Compose runs; pin a sha- tag. | :latest |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessOutdated data