LINE vs Ogave SMS
LINE is an MCP server published by line. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ogave SMS is an MCP server published by ogave.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  Ogave SMS |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:2fe78452545d Forks (GitHub): 160 Pulls (Docker Hub): 25 764 Stars (Docker Hub): 0 Stars (GitHub): 797 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Ogave SMS |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 797 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 25 764 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 160 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/line) | Remote server (app.ogave.co/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/line/line-bot-mcp-server | github.com/ogave-co/sms-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-03 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 33 h ago returned HTTP 405 |
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.
Ogave SMS
Quote, send and track SMS, campaigns, contacts and Verify codes, with a confirmation before sending.
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)
Ogave SMS As a remote MCP server
claude mcp add --transport http sms https://app.ogave.co/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Ogave SMS has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Ogave SMS publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Ogave SMS publish no settings it asks for, so we do not compare settings.
What it can do: LINE · What it can do: Ogave SMS · 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.