Ext Ops Panel
Open dashboard
Comparison

imessage vs phone-sms

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). phone-sms is an MCP server published by h-3303. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceimessagephone-sms
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 3
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (PyPI): 132
Downloads/week (PyPI): 17
Forks (GitHub): 0
Stars (GitHub): 1
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

imessage vs phone-sms
Factimessagephone-sms
Marketplaces that list it11
Stars (GitHub) (differs)25 (better)1 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (phone-sms)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITGPL-3.0-or-later
Repository (differs)github.com/linq-team/claude-code-imessage-channelgithub.com/h-3303/phone-sms
Changes in the last 7 days00
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

imessage

In its own words, on Claude Code: claude-plugins-community:

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.

phone-sms

In its own words, on Official MCP Registry:

Read and send SMS through your own Android phone over KDE Connect on your LAN. No cloud relay.

How to run each

imessage As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install imessage@claude-community

phone-sms As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio phone-sms -- uvx phone-sms

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of imessage publish no settings it asks for, so we do not compare settings.

What it can do: imessage · What it can do: phone-sms · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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