product-playbook vs PAPI: Persistent Adaptive Project Intelligence
product-playbook is a plugin bundle for AI coding tools published by Charles Chen. Marketplaces we read that list it: 1 (Community GitHub marketplaces). PAPI: Persistent Adaptive Project Intelligence is an MCP server published by getpapi. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). 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 |  PAPI: Persistent Adaptive Project Intelligence | |
|---|---|---|
| Community marketplace kaminoikari/product-playbook | Listed Version: 2.4.0 Forks (GitHub): 1 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.402.157 Downloads/month (npm): 3 017 Downloads/week (npm): 776 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.402.157 Downloads/month (npm): 3 017 Downloads/week (npm): 776 Forks (GitHub): 0 Stars (GitHub): 11 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 | product-playbook | PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 25 (better) | 11 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 7 | Not published |
| Parts of the bundle (differs) | 23 | 15 |
| Licence (differs) | MIT | Elastic-2.0 |
| Repository (differs) | github.com/kaminoikari/product-playbook | github.com/getpapi/papi |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen (differs) | 2026-10-24 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-23 |
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
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.
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
How to run each
product-playbook As a Claude Code plugin
/plugin marketplace add kaminoikari/product-playbook
/plugin install product-playbook@product-playbookPAPI: Persistent Adaptive Project Intelligence As a remote MCP server
claude mcp add --transport http papi https://mcp.getpapi.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PAPI: Persistent Adaptive Project Intelligence has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: product-playbook · What it can do: PAPI: Persistent Adaptive Project Intelligence · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.