tgatlas-mcp
Related Servers
Alternatives to tgatlas-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceRead public Telegram channels from AI agents — channel metadata, posts, comments, and search. No MTProto, no Telethon, no api_id.MIT
- AlicenseNot gradedqualityCmaintenanceReads public Telegram channel pages and exposes them as MCP tools over Streamable HTTP/JSON-RPC, enabling retrieval of channel info, latest posts, and search without Telegram API credentials.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing Telegram channels from MCP-capable AI assistants, including drafting and scheduling posts, publishing content, and retrieving channel analytics.MIT
- FlicenseNot gradedqualityCmaintenanceEnables LLM agents to analyze Telegram channels for ad purchasing, providing insights like reach, CPM, and verdicts via MCP tools.-
- AlicenseBqualityDmaintenanceEnables Claude to interact with Telegram channels and groups through API or web scraping for reading posts and searching.1534 npmMIT
- AlicenseAqualityBmaintenanceEnables Telegram analytics (channel stats, search, sentiment) via MCP tools with pay-per-call in USDC, no API keys needed.2025 npm1MIT
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.