Ext Ops Panel
Open dashboard
Comparison

pear vs Local MCP

pear is a plugin bundle for AI coding tools published by Pear. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Local MCP is an MCP server published by local-mcp.com. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
MarketplacepearLocal MCP
Community marketplace ashtonau/pear-plugin Listed
Version: 1.1.1
Forks (GitHub): 1
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.0.421
Downloads/month (npm): 12 527
Downloads/week (npm): 3 012
Forks (GitHub): 12
Stars (GitHub): 73
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 2
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

pear vs Local MCP
FactpearLocal MCP
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)7 (worse)73 (better)
Forks (GitHub) (differs)1 (worse)12 (better)
Last release (differs)2026-10-17 (better)2026-10-13 (worse)
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)510
LicenceMITMIT
Repository (differs)github.com/ashtonau/pear-plugingithub.com/colibird-ai/local-mcp-releases
Changes in the last 7 days (differs)41
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago

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

pear

In its own words, on Community GitHub marketplaces:

Official Pear integration for Claude Code: iCloud Calendar, Contacts, Mail, and legacy CalDAV reminders through hosted MCP tools. Upgraded Apple Reminders are not supported.

Local MCP

In its own words, on Official MCP Registry:

Mac & Windows: let ChatGPT, Claude & Cursor use your email, calendar, iMessage, Teams, files.

How to run each

pear As a Claude Code plugin

Claude Code
/plugin marketplace add ashtonau/pear-plugin
/plugin install pear@pear-marketplace

Local MCP As a remote MCP server

Claude Code
claude mcp add --transport http local-mcp https://local-mcp.com/mcp

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

Only Local MCP has a remote endpoint we check. How we check endpoints

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 pear publish no settings it asks for, so we do not compare settings.

What it can do: pear · What it can do: Local MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.

Where the data comes from: how the catalog is built