Ext Ops Panel
Open dashboard
Comparison

Caelario vs io.github.mrocker/social-data-mcp

Caelario is an MCP server published by chunkydonut21. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrocker/social-data-mcp is an MCP server published by mrocker. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
MarketplaceCaelarioio.github.mrocker/social-data-mcp
Official MCP Registry Listed
Version: 0.1.9
Downloads/month (npm): 134
Downloads/week (npm): 28
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.2.0
Downloads/month (npm): 611
Downloads/week (npm): 104
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.2.0
Downloads/month (npm): 611
Downloads/week (npm): 104
Forks (GitHub): 0
Stars (GitHub): 0
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

Caelario vs io.github.mrocker/social-data-mcp
FactCaelarioio.github.mrocker/social-data-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-11-08 (better)2026-10-18 (worse)
Where it runs (differs)On your machine (caelario-mcp)On your machine (social-data-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/chunkydonut21/caelario-mcpgithub.com/mrocker/social-data-mcp
Changes in the last 7 days (differs)30
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

Caelario

In its own words, on Official MCP Registry:

MCP server for Instagram, TikTok, YouTube, X and Facebook data extraction and automation.

io.github.mrocker/social-data-mcp

In its own words, on Official MCP Registry:

X, YouTube, TikTok and LinkedIn data plus video transcripts in one stdio MCP server. Pay per result.

How to run each

Caelario As a local MCP server: npm package

Claude Code
claude mcp add --env "CAELARIO_API_KEY=<YOUR_CAELARIO_API_KEY>" --transport stdio caelario -- npx -y caelario-mcp

Requires: CAELARIO_API_KEY (secret)

io.github.mrocker/social-data-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio social-data-mcp -- npx -y social-data-mcp

Requires: APIFY_TOKEN (secret)

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

Only Caelario asks for

  • CAELARIO_API_KEY (secret)

Only io.github.mrocker/social-data-mcp asks for

  • APIFY_TOKEN (secret)

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

What it can do: Caelario · What it can do: io.github.mrocker/social-data-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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