Ext Ops Panel
Open dashboard
Comparison

Opine vs CallRail MCP

Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). CallRail MCP is an MCP server published by pghdma. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. 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
MarketplaceOpineCallRail MCP
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: 1.3.1
Downloads/month (PyPI): 582
Downloads/week (PyPI): 168
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.3.1
Downloads/month (PyPI): 582
Downloads/week (PyPI): 168
Forks (GitHub): 0
Stars (GitHub): 2
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 CallRail MCP
FactOpineCallRail MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)22
Forks (GitHub) (differs)4 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (codygreen719/opine-mcp-server)On your machine (callrail-mcp)
Transportstdiostdio
Tools it declares (differs)11Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/cody-docker/opine-mcp-servergithub.com/pghdma/callrail-mcp
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.

CallRail MCP

In its own words, on Official MCP Registry:

CallRail REST API v3: 57 tools for calls, leads, trackers, tags, users, and agency reporting.

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)

CallRail MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "CALLRAIL_API_KEY=<YOUR_CALLRAIL_API_KEY>" --transport stdio callrail-mcp -- uvx callrail-mcp

Requires: CALLRAIL_API_KEY (secret)

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

Tools each declares

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

Settings each asks for

Only Opine asks for

  • OPINE_API_KEY (secret)

Only CallRail MCP asks for

  • CALLRAIL_API_KEY (secret)

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

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