tgatlas-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Alternative to TELEGRAM_API_KEY. RapidAPI key. | |
| TELEGRAM_API_KEY | No | RapidAPI key. RAPIDAPI_KEY also works. | |
| TELEGRAM_API_HOST | No | Upstream host. | telegram155.p.rapidapi.com |
| TELEGRAM_TIMEOUT_MS | No | Per-request timeout. | 30000 |
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 |
|---|---|
| telegram_channelA | Look up a public Telegram channel: title, description, exact subscriber count, creation date, verification and scam flags, and how often it posts. Use to check whether a channel is real, how large it is, and whether it is still alive — a channel with 200k subscribers and nothing published this year is a common and invisible failure. |
| telegram_similar_channelsA | Return the channels Telegram itself recommends alongside a given channel — its own topical judgement, not a keyword match, so it surfaces channels that share an audience without sharing vocabulary. The way to discover channels whose names you do not already know: start from one you do and walk outward. Large channels return roughly a dozen; small or very new ones return none. |
| telegram_search_channelsA | Telegram's own global search over public channels and groups, by title and handle. Good for seeding a topic; telegram_similar_channels is what expands a seed into a neighbourhood. Short topical words work better than sentences. |
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 3 tools
Each tool targets a clearly distinct action: fetching a single channel's details, discovering similar channels via recommendations, and searching Telegram's global index by keyword. There is no functional overlap between the tools, and the descriptions reinforce the differences.
All tool names share the telegram_ prefix, but the suffixes mix a noun (channel), an adjective-noun pair (similar_channels), and a verb-noun pair (search_channels). This is still readable and predictable, with only a minor deviation in grammatical pattern.
Three tools is a well-scoped count for a focused read-only Telegram channel index server. Each tool provides a distinct core capability without redundancy or bloat.
For a read-only directory, the toolset covers the full workflow: search to find a starting channel, retrieve detailed metadata, and expand outward via similar channels. No obvious lifecycle gaps exist because create/update/delete are not relevant to this domain.