Ext Ops Panel
Open dashboard
Comparison

LINE vs ai.izap/whatsapp

LINE is an MCP server published by line. Marketplaces we read that list it: 1 (Docker MCP Catalog). ai.izap/whatsapp is an MCP server published by izap.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
MarketplaceLINEai.izap/whatsapp
Docker MCP Catalog Listed
Version: sha256:2fe78452545d
Forks (GitHub): 156
Pulls (Docker Hub): 25 109
Stars (Docker Hub): 0
Stars (GitHub): 790
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.5.0
No figure published
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 ai.izap/whatsapp
FactLINEai.izap/whatsapp
Marketplaces that list it11
Stars (GitHub) (differs)790No figure on GitHub
Pulls (Docker Hub) (differs)25 109No figure on Docker Hub
Forks (GitHub) (differs)156No figure on GitHub
Last release (differs)Not published2026-10-23
Where it runs (differs)On your machine (mcp/line)Remote server (api.izap.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/line/line-bot-mcp-serverNot stated
Changes in the last 7 days (differs)013
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 30 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

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.

ai.izap/whatsapp

In its own words, on Official MCP Registry:

WhatsApp assistants, messaging, broadcasts, and analytics for your iZap account, over OAuth.

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)

ai.izap/whatsapp As a remote MCP server

Claude Code
claude mcp add --transport http whatsapp https://api.izap.ai/mcp

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

Only ai.izap/whatsapp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of ai.izap/whatsapp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of ai.izap/whatsapp publish no settings it asks for, so we do not compare settings.

What it can do: LINE · What it can do: ai.izap/whatsapp · 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