Opine vs product-playbook
product-playbook is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑03.
Opine is an MCP server published by cody-docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). product-playbook is a plugin bundle for AI coding tools published by Charles Chen. No marketplace we read lists it any more. As of our marketplace pass on 2026-11-06. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:e6e704c00f78 Forks (GitHub): 4 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Community marketplace kaminoikari/product-playbook | Not listed | Removed on 2026-11-03 Version: 2.4.0 Forks (GitHub): 1 Stars (GitHub): 25 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 | product-playbookno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 2 | 25 |
| Forks (GitHub) (differs) | 4 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (codygreen719/opine-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 11 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 7 |
| Parts of the bundle (differs) | Not a bundle | 23 |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/cody-docker/opine-mcp-server | github.com/kaminoikari/product-playbook |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-24 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of product-playbook
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Guide product managers from idea to launch using the Pragmatic Framework (Foundations, Focus, Build). Every stage ends in a client-ready artifact (Markdown or Word .docx).
-
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.
-
Product management skills for Claude Code. Gives Claude structured methodologies for discovery synthesis (JTBD, empathy mapping, journey mapping), user research design (interview…
-
Turn an idea into a buildable plan: product strategy, Claude-Design-grade UX, a PRD map, a wave plan and a Definition of Done.
-
ai-for-product-management-pack
31 skills for deciding what to build, what to drop and whether it worked: prioritising and saying no, setting direction, discovering what customers need, defining the work…
-
Product management agent: 6 skills, 3 agents. Discovery briefs, user research interview guides, PRDs, RICE prioritization, sprint retrospectives, and user story generation.
What each says it does
Opine
A Model Context Protocol (MCP) server for querying deals and evaluations from the Opine CRM API.
product-playbook
MUST use when the user wants to plan, strategize, validate, or scope a product or feature. Composable product-thinking lenses (JTBD, PR-FAQ, positioning, pre-mortem, RICE, North Star, MVP, GTM, and more) that snap to the outcome and blend when the situation needs it, from raw idea to dev handoff.
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-server
Requires: OPINE_API_KEY (secret)
product-playbook
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of product-playbook publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of product-playbook publish no settings it asks for, so we do not compare settings.
What it can do: Opine · What it can do: product-playbook · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.