LINE vs imessage
LINE is an MCP server published by line. Marketplaces we read that list it: 1 (Docker MCP Catalog). imessage is a plugin bundle for AI coding tools published by linq-team. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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 |  imessage |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:2fe78452545d Forks (GitHub): 155 Pulls (Docker Hub): 24 797 Stars (Docker Hub): 0 Stars (GitHub): 786 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.2.0 Forks (GitHub): 3 Stars (GitHub): 25 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 | imessage |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 786 (better) | 25 (worse) |
| Pulls (Docker Hub) (differs) | 24 797 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 155 (better) | 3 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/line) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/line/line-bot-mcp-server | github.com/linq-team/claude-code-imessage-channel |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.
imessage
Two-way iMessage bridge for Claude Code. Send and receive iMessages, photos, reactions, threaded replies, and file attachments directly from your Claude Code session. Powered by Linq's iMessage API with built-in access control (pairing codes, allowlists, open/disabled policies). Supports 15 iMessage effects (confetti, fireworks, etc.), text decorations (bold, italic, animations), rich link previews, SMS/RCS fallback, and capability checks. Auto-sets contact card, sends read receipts and typing indicators.
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)
imessage As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install imessage@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of imessage publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of imessage publish no settings it asks for, so we do not compare settings.
What it can do: LINE · What it can do: imessage · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.