Ext Ops Panel
Open dashboard
Comparison

Opine vs merge-agent-handler

Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). merge-agent-handler is a plugin bundle for AI coding tools published by merge-api. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceOpinemerge-agent-handler
Docker MCP Catalog Listed
Version: sha256:e6e704c00f78
Forks (GitHub): 4
Stars (GitHub): 2
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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 merge-agent-handler
FactOpinemerge-agent-handler
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (codygreen719/opine-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)11Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/cody-docker/opine-mcp-servergithub.com/merge-api/ah-plugins
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.

merge-agent-handler

In its own words, on Claude Code: claude-plugins-community:

Connect Claude Code and Cowork to hundreds of enterprise tools (Jira, Salesforce, HubSpot, Slack, Gong, Workday, etc.) via Merge Agent Handler. 18 MCP tools for managing users, tool packs, connectors, and calling enterprise APIs.

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)

merge-agent-handler As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install merge-agent-handler@claude-community

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

Tools each declares

The marketplaces of merge-agent-handler publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of merge-agent-handler publish no settings it asks for, so we do not compare settings.

What it can do: Opine · What it can do: merge-agent-handler · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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