Ext Ops Panel
Open dashboard
Comparison

Telnyx vs Chatroost — unofficial Telegram MCP server

Telnyx is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Chatroost — unofficial Telegram MCP server is an MCP server published by mcp-telegram. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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

Where each is published
MarketplaceTelnyxChatroost — unofficial Telegram MCP server
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.43.6
Downloads/month (npm): 4 460
Downloads/week (npm): 593
Forks (GitHub): 20
Stars (GitHub): 49
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

Telnyx vs Chatroost — unofficial Telegram MCP server
FactTelnyxChatroost — unofficial Telegram MCP server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub49
Forks (GitHub) (differs)No figure on GitHub20
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (api.telnyx.com/v2/mcp)Remote server (mcp.mcp-telegram.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/mcp-telegram/mcp-telegram
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (41 h ago)Responded 2 days 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

Telnyx

In its own words, on Docker MCP Catalog:

Enables interaction with powerful telephony, messaging, and AI assistant APIs.

Chatroost — unofficial Telegram MCP server

In its own words, on Official MCP Registry:

Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.

How to run each

Telnyx As a remote MCP server

Claude Code
claude mcp add --transport http telnyx https://api.telnyx.com/v2/mcp

Requires: TELNYX_API_KEY (secret)

Chatroost — unofficial Telegram MCP server As a remote MCP server

Claude Code
claude mcp add --transport http mcp-telegram https://mcp.mcp-telegram.com/mcp

Requires: 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 the endpoint of Chatroost — unofficial Telegram MCP server responded at the last daily 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

Only Telnyx asks for

  • TELNYX_API_KEY (secret)

Only Chatroost — unofficial Telegram MCP server asks for

  • TELEGRAM_API_HASH (secret)
  • TELEGRAM_API_ID (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Telnyx · What it can do: Chatroost — unofficial Telegram MCP server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built