Ext Ops Panel
Open dashboard
Comparison

Opine vs BoondManager MCP Server

Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). BoondManager MCP Server is an MCP server published by fauguste. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
MarketplaceOpineBoondManager MCP Server
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: 2.15.2
Downloads/month (npm): 2 633
Downloads/week (npm): 283
Forks (GitHub): 17
Stars (GitHub): 21
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 BoondManager MCP Server
FactOpineBoondManager MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)21 (better)
Forks (GitHub) (differs)4 (worse)17 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (codygreen719/opine-mcp-server)On your machine (boondmanager-mcp-server)
Transportstdiostdio
Tools it declares (differs)11Not published
Environment variables it asks for (differs)1, secrets among them: 114, secrets among them: 5
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/cody-docker/opine-mcp-servergithub.com/fauguste/boondmanager-mcp-server
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

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.

BoondManager MCP Server

In its own words, on Official MCP Registry:

MCP Server for BoondManager API - 182 tools, 12 prompts, 22 resources (ERP/CRM)

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)

BoondManager MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio boondmanager-mcp-server -- npx -y boondmanager-mcp-server

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

Tools each declares

The marketplaces of BoondManager MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only Opine asks for

  • OPINE_API_KEY (secret)

Only BoondManager MCP Server asks for

  • BOOND_API_TOKEN (secret)
  • BOOND_BASE_URL
  • BOOND_CLIENT_KEY (secret)
  • BOOND_CLIENT_TOKEN (secret)
  • BOOND_DICTIONARY_OVERRIDES
  • BOOND_MCP_CONFIRM_DELETE
  • BOOND_MCP_DOMAINS
  • BOOND_MCP_EXCLUDE_DOMAINS
  • BOOND_MCP_OPERATIONS
  • BOOND_MCP_PROFILE
  • BOOND_MCP_READ_ONLY
  • BOOND_PASSWORD (secret)
Show the remaining 2
  • BOOND_USER
  • BOOND_USER_TOKEN (secret)

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

What it can do: Opine · What it can do: BoondManager MCP Server · 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