Personal Telegram MCP
by t4god
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOT_ROOT | Yes | The runtime directory for the server. It must match the directory used during setup. | |
| DOT_BASE_URL | Yes | The external HTTPS origin for the server, without /mcp. It must match the external origin exactly. | |
| DOT_OWNER_ID | Yes | The numeric Telegram owner ID printed by setup. | |
| DOT_SEND_ENABLED | No | Set to true to enable sending and replying. Setting it to false disables sends without removing read/event features. | |
| DOT_OAUTH_REDIRECT_URIS | No | Comma-separated exact HTTPS OAuth callback URIs for clients that need their callback configured. Do not use wildcard callback domains. | |
| DOT_BACKGROUND_MONITORING_ENABLED | No | Set to true to enable background event capture. Events are retained for up to 30 days or 100,000 events. |
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
ResponsivenessNo recent community issues