Ext Ops Panel
Open dashboard
Comparison

consensus vs PAPI: Persistent Adaptive Project Intelligence

consensus is a plugin bundle for AI coding tools published by Consensus. 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: 2 (Official MCP Registry, Community GitHub marketplaces). 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
MarketplaceconsensusPAPI: Persistent Adaptive Project Intelligence
Community marketplace masterblaster14/consensus Listed
Version: 0.1.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.402.35
Downloads/month (npm): 1 396
Downloads/week (npm): 100
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

consensus vs PAPI: Persistent Adaptive Project Intelligence
FactconsensusPAPI: Persistent Adaptive Project Intelligence
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub11
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.getpapi.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle33
LicenceMITMIT
Repository (differs)github.com/masterblaster14/consensusgithub.com/getpapi/papi
Changes in the last 7 days22
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

consensus

In its own words, on Community GitHub marketplaces:

Declare plans before writing code, share memory between agents, and let humans rule on conflicts once. Adds the Consensus MCP server, a hook that refuses edits until the plan is declared, and a workflow skill.

PAPI: Persistent Adaptive Project Intelligence

In its own words, on Official MCP Registry:

Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.

How to run each

consensus As a Claude Code plugin

Claude Code
/plugin marketplace add masterblaster14/consensus
/plugin install consensus@consensus

PAPI: Persistent Adaptive Project Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http papi https://mcp.getpapi.ai/mcp

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

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: consensus · 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. 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