Ext Ops Panel
Open dashboard
Comparison

LINE vs Better-TG-CLI (Telegram)

LINE is an MCP server published by line. Marketplaces we read that list it: 1 (Docker MCP Catalog). Better-TG-CLI (Telegram) is an MCP server published by TheVilfer. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
MarketplaceLINEBetter-TG-CLI (Telegram)
Docker MCP Catalog Listed
Version: sha256:2fe78452545d
Forks (GitHub): 156
Pulls (Docker Hub): 24 812
Stars (Docker Hub): 0
Stars (GitHub): 788
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.37.0
Downloads/month (npm): 5 157
Downloads/week (npm): 964
Forks (GitHub): 3
Stars (GitHub): 3
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

LINE vs Better-TG-CLI (Telegram)
FactLINEBetter-TG-CLI (Telegram)
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)788 (better)3 (worse)
Pulls (Docker Hub) (differs)24 812No figure on Docker Hub
Forks (GitHub) (differs)156 (better)3 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/line)On your machine (better-tg-cli)
Transportstdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/line/line-bot-mcp-servergithub.com/thevilfer/better-tg-cli
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11

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

In its own words, on Docker MCP Catalog:

MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.

Better-TG-CLI (Telegram)

In its own words, on Official MCP Registry:

Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.

How to run each

LINE As a local MCP server: Docker image

Claude Code
claude mcp add --env "CHANNEL_ACCESS_TOKEN=<YOUR_CHANNEL_ACCESS_TOKEN>" --transport stdio line -- docker run -i --rm -e CHANNEL_ACCESS_TOKEN mcp/line

Requires: CHANNEL_ACCESS_TOKEN (secret)

Better-TG-CLI (Telegram) As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio better-tg-cli -- npx -y better-tg-cli mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Better-TG-CLI (Telegram) 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 Better-TG-CLI (Telegram) asks for

  • TG_PROFILE

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

What it can do: LINE · What it can do: Better-TG-CLI (Telegram) · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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