A
licenseA
qualityD
maintenanceEnables AI assistants to publish, edit, search, and manage messages in Telegram channels via a set of MCP tools.
8
MIT
tg-archive
by myshli
Related Servers
Alternatives to tg-archive
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants like Claude to read, search, and send messages through your personal Telegram account via MCP tools.MIT
- AlicenseBqualityDmaintenanceEnables Claude to interact with Telegram channels and groups through API or web scraping for reading posts and searching.1538 npmMIT
- AlicenseBqualityDmaintenanceEnables users to read, search, and manage Telegram messages in channels, groups, and private chats through MCP tools.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search a public Facebook post archive using keyword, semantic, and hybrid retrieval, browse recently indexed posts, and fetch individual post records with source links through read-only MCP tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients such as Claude and Cursor to access and manage Telegram accounts, chats, messages, contacts, media, folders, and admin operations through exposed tools.Apache 2.0
TDQS
A3.6/5.0
Scored across 5 tools
Disambiguation4/5
get_post, list_topics, and stats are clearly distinct, and the descriptions even prescribe a workflow (list_topics → search_posts → get_post). The only mild overlap is between recent (time-windowed browsing) and search_posts (query-based retrieval), both returning filtered post lists, but the time-vs-query distinction is documented well enough to separate them.
Naming Consistency3/5
Two tools use the verb_noun pattern (get_post, list_topics) while the other three are bare nouns or adjectives (recent, stats, search_posts), and 'recent' in particular reads more like a parameter than a tool name. The set is still readable and unambiguous, but the convention is mixed.
Tool Count5/5
Five tools is a tight, well-scoped surface for a read-only archive server: discovery (list_topics, stats), retrieval (search_posts, recent), and expansion (get_post). Each tool has a clear job and none feels redundant.
Completeness4/5
The read-only lifecycle is covered end to end: find filters, search, browse recent, expand full text, and inspect corpus stats. Minor gaps remain — no explicit channel-enumeration tool (channels must be guessed or inferred from stats) and no pagination/offset control on search or recent results for large result sets.
Maintenance
ActivityMaintained
ResponsivenessNo issues