telegram-topics vs AdminHub for Telegram
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. AdminHub for Telegram is an MCP server published by adminhub.tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 | ||
|---|---|---|
| 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.1.0 No figure published 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 · | AdminHub for Telegram |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (backend-git-production-cb93.up.railway.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/behindthebeat/claude-telegram-topics | github.com/siteboss777-lgtm/telegram-admin-hub |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 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.
-
Multi-session Telegram channel for Claude Code — daemon-based architecture with session routing, /new, /sessions, /kill commands from Telegram.
-
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.
AdminHub for Telegram
Run a Telegram channel from your AI agent. Posts go out through your own bot, not your 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.
AdminHub for Telegram As a remote MCP server
claude mcp add --transport http telegram https://backend-git-production-cb93.up.railway.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only AdminHub for Telegram 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
Neither one's marketplaces publish the settings it asks for.
What it can do: telegram-topics · What it can do: AdminHub for Telegram · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.