Telegram Notifications MCP
by gmoz22
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_MCP_HOST | No | HTTP bind address (127.0.0.1; 0.0.0.0 in Docker). | 127.0.0.1 |
| TELEGRAM_MCP_PORT | No | HTTP port, default 3000. | 3000 |
| TELEGRAM_NOTIF_CONFIG | No | Inline JSON config; overrides any file. | |
| TELEGRAM_MCP_ADMIN_KEY | No | Hosted admin key (32-256 of A-Z a-z 0-9 - _); replaces the managed key. Coolify sets it. | |
| TELEGRAM_MCP_ALLOWED_HOSTS | No | Comma-separated hostnames accepted over HTTP, such as notify.example.com. | |
| TELEGRAM_NOTIF_CONFIG_FILE | No | Config file path (e.g., /data/config.json in Docker). | |
| TELEGRAM_MCP_ALLOWED_ORIGINS | No | Optional browser origins to allow. | |
| TELEGRAM_MCP_DISCOVERY_ENABLED | No | Set to 'true' or 'false'; overrides discovery.enabled when set. |
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
ActivityNo data
ResponsivenessOutdated data