Ext Ops Panel
Open dashboard
Comparison

claude-chat-search vs iMessage History

claude-chat-search is a plugin bundle for AI coding tools published by danutmitrut. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). iMessage History is an MCP server published by anipotts. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. 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
Marketplaceclaude-chat-searchiMessage History
Claude Code: claude-plugins-community Listed
Version: b75501a
Forks (GitHub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.3.1
Downloads/month (npm): 1 951
Downloads/week (npm): 147
Forks (GitHub): 7
Stars (GitHub): 28
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 3.3.2
Downloads/month (npm): 1 951
Downloads/week (npm): 147
Forks (GitHub): 7
Stars (GitHub): 28
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

claude-chat-search vs iMessage History
Factclaude-chat-searchiMessage History
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)9 (worse)28 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last release (differs)Not published2026-10-24
Where it runs (differs)Installs as a plugin bundleOn your machine (imessage-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 0
Parts of the bundle11
Licence (differs)Not statedMIT
Repository (differs)github.com/danutmitrut/claude-chat-searchgithub.com/anipotts/imessage-mcp
Changes in the last 7 days (differs)09
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

claude-chat-search

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

Full-text search across all Claude Code conversations. Search through conversation content including messages, tool results, and code — find any past discussion instantly. Works locally, no external services needed.

iMessage History

In its own words, on Official MCP Registry:

Read-only MCP server for searching and reading Apple Messages history on macOS.

How to run each

claude-chat-search As a Claude Code plugin

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

iMessage History As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio imessage-mcp -- npx -y imessage-mcp

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

What it can do: claude-chat-search · What it can do: iMessage History · 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. Package data comes from the public npm registry (registry.npmjs.org). 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