telegram-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_API_ID | No | Your Telegram API ID from my.telegram.org | |
| TELEGRAM_API_HASH | No | Your Telegram API hash from my.telegram.org | |
| TELEGRAM_DATA_PATH | No | Override path for storing session data and cookies |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_channelB | Scrape a Telegram channel and return posts in markdown format. Uses authenticated session if logged in. |
| scrape_channel_fullA | Scrape ALL posts from a Telegram channel and save to file. Uses authenticated session if logged in. Returns file location. |
| scrape_groupB | Scrape a Telegram group and return posts in markdown format. Uses authenticated session if logged in. |
| get_channel_infoA | Get only the channel/group information without scraping posts. Uses authenticated session if logged in. |
| scrape_date_rangeB | Scrape posts within a specific date range. Uses authenticated session if logged in. |
| telegram_loginC | Authenticate with Telegram Web to access restricted content |
| telegram_logoutB | Clear Telegram authentication cookies |
| telegram_auth_statusB | Check if authenticated with Telegram |
| scrape_channel_authenticatedB | Scrape a Telegram channel using authenticated session (can access restricted content) |
| scrape_manualA | Manual scraping mode: Opens browser for you to login and navigate to any channel, then scrapes it |
| telegram_api_loginC | Login to Telegram using API credentials for fast, efficient scraping |
| api_scrape_channelC | Scrape a Telegram channel using the API (fast and efficient) |
| api_search_channelC | Search for messages within a Telegram channel |
| api_get_channel_infoC | Get detailed information about a Telegram channel using the API |
| api_logoutB | Disconnect from Telegram API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Multiple tools overlap in purpose (scrape_channel, scrape_channel_authenticated, api_scrape_channel) but descriptions differentiate by authentication method. Still, an agent may struggle to choose the right one at a glance.
Naming is inconsistent: snake_case verbs (scrape_channel) mixed with prefixed styles (telegram_login, api_scrape_channel). No uniform verb_noun pattern across the suite.
15 tools is on the higher end but acceptable for the range of authentication methods and scraping modes. Each tool adds some functionality, though redundancy inflates the count.
Covers channel/group scraping, date ranges, full exports, search, info retrieval, and authentication. Minor gaps like batch operations or message sending are outside the core scraping purpose.