telegram-topics vs Chatroost — unofficial Telegram MCP server
telegram-topics is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
telegram-topics is a plugin bundle for AI coding tools published by takumi. No marketplace we read lists it any more. Chatroost — unofficial Telegram MCP server is an MCP server published by mcp-telegram. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Chatroost — unofficial Telegram MCP server | |
|---|---|---|
| Community marketplace behindthebeat/claude-telegram-topics | Removed on 2026-10-15 Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.44.1 Downloads/month (npm): 3 603 Downloads/week (npm): 744 Forks (GitHub): 21 Stars (GitHub): 60 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.44.1 Downloads/month (npm): 3 603 Downloads/week (npm): 744 Forks (GitHub): 21 Stars (GitHub): 60 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | telegram-topicsno longer listed · | Chatroost — unofficial Telegram MCP server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 1 | 60 |
| Forks (GitHub) (differs) | 0 | 21 |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 2 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/behindthebeat/claude-telegram-topics | github.com/mcp-telegram/mcp-telegram |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 26 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of telegram-topics
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Run a Telegram channel from your AI agent. Posts go out through your own bot, not your account.
-
Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach…
-
Connect a Telegram bot to your Claude Code session over MCP. The server logs in as a bot, forwards inbound messages into the session as <channel> notifications, and exposes tools…
-
Telegram channels you administer: analytics, content plans, scheduled publishing. No userbot
-
telegram com.jojapi/telegram
Telegram: FASTEST real time Telegram API. Retrieve channel's info and messages in milliseconds..
-
Full-spectrum Telegram access for coding agents through the tg-agent CLI: channels, chats, messages, media, admin, content pipelines, analytics.
What each says it does
telegram-topics
Telegram channel for Claude Code — messaging bridge with built-in access control and topic-based session routing.
Chatroost — unofficial Telegram MCP server
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
How to run each
telegram-topics
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Chatroost — unofficial Telegram MCP server As a remote MCP server
claude mcp add --transport http mcp-telegram https://mcp.mcp-telegram.com/mcpRequires: TELEGRAM_API_HASH (secret), TELEGRAM_API_ID (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Chatroost — unofficial Telegram MCP server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of telegram-topics publish no settings it asks for, so we do not compare settings.
What it can do: telegram-topics · What it can do: Chatroost — unofficial Telegram MCP server · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.