Chatroost — unofficial Telegram MCP server vs Telethon Plus
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)). Telethon Plus is an MCP server published by psyb0t. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  Chatroost — unofficial Telegram MCP server |  Telethon Plus |
|---|---|---|
| Official MCP Registry | Listed Version: 1.44.1 Downloads/month (npm): 3 603 Downloads/week (npm): 744 Forks (GitHub): 21 Stars (GitHub): 60 Not marked · First seen |
Listed Version: 0.5.7 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.44.1 Downloads/month (npm): 3 603 Downloads/week (npm): 744 Forks (GitHub): 21 Stars (GitHub): 60 Not marked · First seen |
Not listed |
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 | Chatroost — unofficial Telegram MCP server | Telethon Plus |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 60 (better) | 4 (worse) |
| Forks (GitHub) (differs) | 21 (better) | 1 (worse) |
| Last release (differs) | 2026-10-26 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (docker.io/psyb0t/telethon-plus:v0.5.7) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mcp-telegram/mcp-telegram | github.com/psyb0t/docker-telethon-plus |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 22 h ago, requires a key | no remote endpoint we check |
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
Chatroost — unofficial Telegram MCP server
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
Telethon Plus
Self-hosted MCP server: Telegram userbot control (Telethon) via HTTP and MCP.
How to run each
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)
Telethon Plus
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 Telethon Plus publish no settings it asks for, so we do not compare settings.
What it can do: Chatroost — unofficial Telegram MCP server · What it can do: Telethon Plus · Compare two other plugins
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.