Ext Ops Panel
Open dashboard
Comparison

Slack (Archived) vs iMessage History

Slack (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). iMessage History is an MCP server published by anipotts. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
MarketplaceSlack (Archived)iMessage History
Docker MCP Catalog Listed
Version: sha256:4cc10c3f4bd9
Forks (GitHub): 11 788
Pulls (Docker Hub): 312 700
Stars (Docker Hub): 25
Stars (GitHub): 91 289
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.2.0
Downloads/month (npm): 3 131
Downloads/week (npm): 246
Forks (GitHub): 6
Stars (GitHub): 27
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

Slack (Archived) vs iMessage History
FactSlack (Archived)iMessage History
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 289 (better)27 (worse)
Pulls (Docker Hub) (differs)312 700No figure on Docker Hub
Forks (GitHub) (differs)11 788 (better)6 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/slack)On your machine (imessage-mcp)
Transportstdiostdio
Tools it declares (differs)8Not published
Environment variables it asks for (differs)3, secrets among them: 15, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/anipotts/imessage-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

Slack (Archived)

In its own words, on Docker MCP Catalog:

Interact with Slack Workspaces over the Slack API.

iMessage History

In its own words, on Official MCP Registry:

Search and read your Apple Messages history from any MCP client. Read-only, local.

How to run each

Slack (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "SLACK_BOT_TOKEN=<YOUR_SLACK_BOT_TOKEN>" --transport stdio slack -- docker run -i --rm -e SLACK_BOT_TOKEN mcp/slack

Requires: SLACK_BOT_TOKEN (secret)

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

The marketplaces of iMessage History publish no list of tools, so we do not compare tools.

Settings each asks for

Only Slack (Archived) asks for

  • SLACK_BOT_TOKEN (secret)
  • SLACK_CHANNEL_IDS
  • SLACK_TEAM_ID

Only iMessage History asks for

  • IMESSAGE_CACHE
  • IMESSAGE_CONTACTS
  • IMESSAGE_DB
  • IMESSAGE_PRIVACY
  • IMESSAGE_UPDATE_CHECK

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Slack (Archived) · What it can do: iMessage History · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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