Telegram Lead Analysis MCP
by zeropennyads
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport (set by Railway) | |
| LEADS_SOURCE | No | Data source: 'auto' (default) uses live if credentials present, 'json' uses export file | auto |
| TELEGRAM_API_ID | No | Telegram API ID for live mode | |
| TELEGRAM_SESSION | No | Telegram session string for live mode | |
| TELEGRAM_API_HASH | No | Telegram API hash for live mode | |
| LEADS_WHITELIST_JSON | No | Optional inline JSON array of lead chat names, overrides config/whitelist.json | |
| TELEGRAM_FETCH_LIMIT | No | Optional fetch limit for Telegram messages, default 500 | 500 |
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
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/zeropennyads/Telegram-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server