Ext Ops Panel
Open dashboard
Comparison

Opine vs io.campaignstack/campaignstack

Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.campaignstack/campaignstack is an MCP server published by campaignstack.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceOpineio.campaignstack/campaignstack
Docker MCP Catalog Listed
Version: sha256:e6e704c00f78
Forks (GitHub): 4
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

Opine vs io.campaignstack/campaignstack
FactOpineio.campaignstack/campaignstack
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)4No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (codygreen719/opine-mcp-server)Remote server (mcp.campaignstack.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)11Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/cody-docker/opine-mcp-serverNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 13 h ago, requires a key

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

Opine

In its own words, on Docker MCP Catalog:

A Model Context Protocol (MCP) server for querying deals and evaluations from the Opine CRM API.

io.campaignstack/campaignstack

In its own words, on Official MCP Registry:

Run B2B outreach from your AI agent: 250+ tools for campaigns, leads, LinkedIn and email workflows.

How to run each

Opine As a local MCP server: Docker image

Claude Code
claude mcp add --env "OPINE_API_KEY=<YOUR_OPINE_API_KEY>" --transport stdio opine-mcp-server -- docker run -i --rm -e OPINE_API_KEY codygreen719/opine-mcp-server

Requires: OPINE_API_KEY (secret)

io.campaignstack/campaignstack As a remote MCP server

Claude Code
claude mcp add --transport http campaignstack https://mcp.campaignstack.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only io.campaignstack/campaignstack has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.campaignstack/campaignstack publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.campaignstack/campaignstack publish no settings it asks for, so we do not compare settings.

What it can do: Opine · What it can do: io.campaignstack/campaignstack · 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. 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