Ext Ops Panel
Open dashboard
Comparison

Meta Council vs Opik

Meta Council is an MCP server published by meta-council.com. Marketplaces we read that list it: 1 (Official MCP Registry). Opik is an MCP server published by comet-ml. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, PyPI (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
MarketplaceMeta CouncilOpik
Official MCP Registry Listed
Version: 1.4.0
No figure published
Not marked · First seen
Listed
Version: 3.0.9
Downloads/month (PyPI): 3 591
Downloads/week (PyPI): 778
Forks (GitHub): 37
Stars (GitHub): 226
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:0e0d7d33d5eb
Forks (GitHub): 37
Pulls (Docker Hub): 17 393
Stars (Docker Hub): 1
Stars (GitHub): 226
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 3.0.9
Downloads/month (PyPI): 3 591
Downloads/week (PyPI): 778
Forks (GitHub): 37
Stars (GitHub): 226
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

Meta Council vs Opik
FactMeta CouncilOpik
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub226
Pulls (Docker Hub) (differs)No figure on Docker Hub17 393
Forks (GitHub) (differs)No figure on GitHub37
Last release (differs)Not published2026-11-07
Where it runs (differs)Remote server (meta-council.com/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declares (differs)Not published13
Environment variables it asks for (differs)Not published4, secrets among them: 1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/daliu/meta-councilgithub.com/comet-ml/opik-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 15 h agoResponded 2 h ago, requires authentication

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

Meta Council

In its own words, on Official MCP Registry:

Multi-expert decision intelligence with transparent synthesis and auditable workflows.

Opik

In its own words, on Official MCP Registry:

Read and score Opik traces, experiments, datasets and prompts from your AI assistant.

How to run each

Meta Council As a remote MCP server

Claude Code
claude mcp add --transport http decision-intelligence https://meta-council.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

Opik As a remote MCP server

Claude Code
claude mcp add --transport http opik-mcp https://www.comet.com/opik/api/v1/mcp

Requires: OPIK_API_KEY (secret)

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of Meta Council publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Meta Council publish no settings it asks for, so we do not compare settings.

What it can do: Meta Council · What it can do: Opik · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.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