LINE vs Chatroost — unofficial Telegram MCP server
LINE is an MCP server published by line. 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-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 |  LINE |  Chatroost — unofficial Telegram MCP server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:2fe78452545d Forks (GitHub): 157 Pulls (Docker Hub): 24 894 Stars (Docker Hub): 0 Stars (GitHub): 789 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.43.6 Downloads/month (npm): 4 519 Downloads/week (npm): 1 284 Forks (GitHub): 20 Stars (GitHub): 47 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 | LINE | Chatroost — unofficial Telegram MCP server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 789 (better) | 47 (worse) |
| Pulls (Docker Hub) (differs) | 24 894 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 157 (better) | 20 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/line) | Remote server (mcp.mcp-telegram.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 2, secrets among them: 2 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/line/line-bot-mcp-server | github.com/mcp-telegram/mcp-telegram |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 24 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
LINE
MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.
Chatroost — unofficial Telegram MCP server
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
How to run each
LINE As a local MCP server: Docker image
claude mcp add --env "CHANNEL_ACCESS_TOKEN=<YOUR_CHANNEL_ACCESS_TOKEN>" --transport stdio line -- docker run -i --rm -e CHANNEL_ACCESS_TOKEN mcp/lineRequires: CHANNEL_ACCESS_TOKEN (secret)
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)
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
The marketplaces of Chatroost — unofficial Telegram MCP server publish no list of tools, so we do not compare tools.
Settings each asks for
Only LINE asks for
CHANNEL_ACCESS_TOKEN (secret)DESTINATION_USER_ID
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: LINE · 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.