Opine vs Juno AI Customer Research
Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Juno AI Customer Research is an MCP server published by hey-juno. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
| Marketplace |   Opine |  Juno AI Customer Research |
|---|---|---|
| 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.0.0 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | Opine | Juno AI Customer Research |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (codygreen719/opine-mcp-server) | Remote server (api.heyjuno.co/v1/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 11 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/cody-docker/opine-mcp-server | github.com/hey-juno/juno-agent-toolkit |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 7 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
A Model Context Protocol (MCP) server for querying deals and evaluations from the Opine CRM API.
Juno AI Customer Research
AI-moderated qualitative customer interviews, study authoring, participant links, and CSV exports.
How to run each
Opine As a local MCP server: Docker image
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-serverRequires: OPINE_API_KEY (secret)
Juno AI Customer Research As a remote MCP server
claude mcp add --transport http juno https://api.heyjuno.co/v1/mcp/Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Juno AI Customer Research has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Juno AI Customer Research publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Juno AI Customer Research publish no settings it asks for, so we do not compare settings.
What it can do: Opine · What it can do: Juno AI Customer Research · 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.