evolve-loop vs PAPI: Persistent Adaptive Project Intelligence
evolve-loop is a plugin bundle for AI coding tools published by mickeyyaya. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
| Marketplace |  evolve-loop |  PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 8.11.1 Forks (GitHub): 2 Stars (GitHub): 5 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
| Fact | evolve-loop | PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 5 (worse) | 11 (better) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.getpapi.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 9 | 3 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/mickeyyaya/evolve-loop | github.com/getpapi/papi |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not 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
evolve-loop
A self-learning development pipeline that gets smarter with every cycle. It calibrates itself against your codebase, dynamically selects the highest-impact tasks, implements them in isolated git worktrees, and blocks bad code through eval gates — then learns from each cycle to make better decisions next time. 4 specialized agents (Scout, Builder, Auditor, Operator) work across 5 phases: DISCOVER → BUILD → AUDIT → SHIP → LEARN. The Scout uses multi-armed bandit scoring and 8-dimension quality benchmarks to target your codebase's weakest areas. The Builder implements in isolation. The Auditor blocks MEDIUM+ severity issues. After each cycle, the pipeline extracts reusable "instincts" — patterns about what worked and what failed — that compound over time. Every 5 cycles, a meta-cycle evaluates the pipeline itself and evolves its own agent prompts based on measured performance. It ran 151 cycles on its own codebase, shipping 67+ improvements and raising its quality score from 83.8 to 94.4 — all autonomously. No e
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
How to run each
evolve-loop As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install evolve-loop@claude-communityPAPI: 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.
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: evolve-loop · What it can do: PAPI: Persistent Adaptive Project Intelligence · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.