dev-loop vs PAPI: Persistent Adaptive Project Intelligence
dev-loop is a plugin bundle for AI coding tools published by choiyounggi. 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-21. 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 |   dev-loop |  PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Community marketplace davepoon/buildwithclaude | Listed Version: 1.33.0 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.402.157 Downloads/month (npm): 1 274 Downloads/week (npm): 106 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 | dev-loop | PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 6 (worse) | 11 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| 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 (differs) | 3, secrets among them: 0 | Not published |
| Hooks it runs (differs) | 13 | Not published |
| Parts of the bundle (differs) | 27 | 15 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/choiyounggi/dev-loop | github.com/getpapi/papi |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days 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
dev-loop
Multi-agent orchestration grounded in an LLM wiki. /dev-loop:orchestrate splits one goal into a dependency graph of parallel Claude Code sessions, each in its own worktree, and supervises them natively on Orca (a tracked Task + Dispatch per phase, pushed worker_done / question / escalation events instead of polling, stall detection; raw tmux fallback). Every plan decision must cite a page in a bundled best-practice wiki of 400+ pages across 10 domains, checked by machine gates and a fresh-context plan reviewer. Insights from your sessions are queued and turned into reviewed wiki PRs when you run /dev-loop:knowledge-flush (automatic flushing is opt-in and never bypasses permission checks).
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
How to run each
dev-loop As a Claude Code plugin
/plugin marketplace add davepoon/buildwithclaude
/plugin install dev-loop@buildwithclaudePAPI: 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
The marketplaces of PAPI: Persistent Adaptive Project Intelligence publish no settings it asks for, so we do not compare settings.
What it can do: dev-loop · 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.