Ext Ops Panel
Open dashboard
Comparison

imessage vs fmsg

imessage is a plugin bundle for AI coding tools published by anthropics. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). fmsg is an MCP server published by markmnl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplaceimessagefmsg
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 4 390
Stars (GitHub): 40 325
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.1
Downloads/month (npm): 2 251
Downloads/week (npm): 1 240
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 fmsg
Factimessagefmsg
Marketplaces that list it11
Stars (GitHub) (differs)40 325 (better)1 (worse)
Forks (GitHub) (differs)4 390 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleOn your machine (@markmnl/fmsg-mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/markmnl/fmsg-mcp
Changes in the last 7 days (differs)02
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-official:

iMessage messaging bridge with built-in access control. Reads chat.db directly, sends via AppleScript. Manage pairing, allowlists, and policy via /imessage:access.

fmsg

In its own words, on Official MCP Registry:

Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.

How to run each

imessage As a Claude Code plugin

Claude Code
/plugin install imessage@claude-plugins-official

fmsg

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: FMSG_API_KEY (secret), FMSG_API_URL

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: fmsg · Compare two other plugins

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