Ext Ops Panel
Open dashboard
Comparison

io.github.mikusnuz/meta vs io.github.pjpoulose/pil

io.github.mikusnuz/meta is an MCP server published by mikusnuz. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). io.github.pjpoulose/pil is an MCP server published by pjpoulose. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceio.github.mikusnuz/metaio.github.pjpoulose/pil
Official MCP Registry Listed
Version: 2.2.2
Downloads/month (npm): 500
Downloads/week (npm): 189
Forks (GitHub): 13
Stars (GitHub): 30
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 348
Downloads/week (PyPI): 28
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Listed
Version: 2.2.2
Downloads/month (npm): 500
Downloads/week (npm): 189
Forks (GitHub): 13
Stars (GitHub): 30
Not marked · First seen
Not listed

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

io.github.mikusnuz/meta vs io.github.pjpoulose/pil
Factio.github.mikusnuz/metaio.github.pjpoulose/pil
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)30 (better)2 (worse)
Forks (GitHub) (differs)13 (better)0 (worse)
Last release (differs)2026-10-20Not published
Where it runs (differs)On your machine (@mikusnuz/meta-mcp)On your machine (personal-instagram-library)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 4Not published
Licence (differs)MITNot stated
Repository (differs)github.com/mikusnuz/meta-mcpgithub.com/pjpoulose/pil
Changes in the last 7 days00
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

io.github.mikusnuz/meta

In its own words, on Official MCP Registry:

MCP server for Instagram Graph API, Threads API & Meta platform management

io.github.pjpoulose/pil

In its own words, on Official MCP Registry:

PIL: local-first knowledge base for your Instagram saved posts, with a read-only MCP server.

How to run each

io.github.mikusnuz/meta As a local MCP server: npm package

Claude Code
claude mcp add --env "INSTAGRAM_ACCESS_TOKEN=<YOUR_INSTAGRAM_ACCESS_TOKEN>" --env "INSTAGRAM_MESSAGING_ACCESS_TOKEN=<YOUR_INSTAGRAM_MESSAGING_ACCESS_TOKEN>" --env "META_APP_SECRET=<YOUR_META_APP_SECRET>" --env "THREADS_ACCESS_TOKEN=<YOUR_THREADS_ACCESS_TOKEN>" --transport stdio meta -- npx -y @mikusnuz/meta-mcp

Requires: INSTAGRAM_ACCESS_TOKEN (secret), INSTAGRAM_MESSAGING_ACCESS_TOKEN (secret), META_APP_SECRET (secret), THREADS_ACCESS_TOKEN (secret)

io.github.pjpoulose/pil As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio pil -- uvx personal-instagram-library

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 io.github.pjpoulose/pil publish no settings it asks for, so we do not compare settings.

What it can do: io.github.mikusnuz/meta · What it can do: io.github.pjpoulose/pil · 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