Telnyx vs Telegram MCP Server
Telnyx is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Telegram MCP Server is an MCP server published by tolboy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.17.3 Forks (GitHub): 2 Stars (GitHub): 10 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 | Telnyx | Telegram MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 10 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | Remote server (api.telnyx.com/v2/mcp) | On your machine (ghcr.io/tolboy/telegram-mcp-tdlib:1.17.3-stdio) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 7, secrets among them: 4 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/tolboy/telegram-mcp-tdlib |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (3 days ago) | 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
Telnyx
Enables interaction with powerful telephony, messaging, and AI assistant APIs.
Telegram MCP Server
Local-first TDLib Telegram MCP server with 115 tools, account isolation and production guardrails.
How to run each
Telnyx As a remote MCP server
claude mcp add --transport http telnyx https://api.telnyx.com/v2/mcp
Requires: TELNYX_API_KEY (secret)
Telegram MCP Server As a local MCP server: Docker image
claude mcp add --env "TDLIB_2FA_PASSWORD=<YOUR_TDLIB_2FA_PASSWORD>" --env "TDLIB_API_HASH=<YOUR_TDLIB_API_HASH>" --env "TDLIB_API_ID=<YOUR_TDLIB_API_ID>" --env "TDLIB_AUTH_CODE=<YOUR_TDLIB_AUTH_CODE>" --env "TDLIB_PHONE_NUMBER=<YOUR_TDLIB_PHONE_NUMBER>" --transport stdio telegram-mcp-tdlib -- docker run -i --rm -e TDLIB_2FA_PASSWORD -e TDLIB_API_HASH -e TDLIB_API_ID -e TDLIB_AUTH_CODE -e TDLIB_PHONE_NUMBER ghcr.io/tolboy/telegram-mcp-tdlib:1.17.3-stdio
Requires: TDLIB_2FA_PASSWORD (secret), TDLIB_API_HASH (secret), TDLIB_API_ID, TDLIB_AUTH_CODE (secret), TDLIB_PHONE_NUMBER (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Telnyx 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
Only Telnyx asks for
TELNYX_API_KEY (secret)
Only Telegram MCP Server asks for
MCP_READ_ONLYMCP_TOOL_PROFILETDLIB_2FA_PASSWORD (secret)TDLIB_API_HASH (secret)TDLIB_API_IDTDLIB_AUTH_CODE (secret)TDLIB_PHONE_NUMBER (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Telnyx · What it can do: 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.