telegram-sessions vs AdminHub for Telegram
telegram-sessions is a plugin bundle for AI coding tools published by bergamolt. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  telegram-sessions | |
|---|---|---|
| Community marketplace bergamolt/telegram-sessions | Listed Version: 0.4.2 Forks (GitHub): 1 Stars (GitHub): 4 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-sessions | AdminHub for Telegram |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | 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 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bergamolt/telegram-sessions | github.com/siteboss777-lgtm/telegram-admin-hub |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 44 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
telegram-sessions
Multi-session Telegram channel for Claude Code — daemon-based architecture with session routing, /new, /sessions, /kill commands from Telegram.
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-sessions As a Claude Code plugin
/plugin marketplace add bergamolt/telegram-sessions
/plugin install telegram-sessions@telegram-sessions-marketplaceAdminHub 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-sessions · 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.