Ext Ops Panel
Open dashboard
Comparison

guild vs PAPI: Persistent Adaptive Project Intelligence

guild is a plugin bundle for AI coding tools published by lookatitude. 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-22. 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
MarketplaceguildPAPI: Persistent Adaptive Project Intelligence
Claude Code: claude-plugins-community Listed
Version: 2.6.0
Forks (GitHub): 0
Stars (GitHub): 7
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

guild vs PAPI: Persistent Adaptive Project Intelligence
FactguildPAPI: Persistent Adaptive Project Intelligence
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (worse)11 (better)
Forks (GitHub)00
Last release (differs)Not published2026-10-15
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)24Not published
Parts of the bundle (differs)14715
LicenceMITMIT
Repository (differs)github.com/lookatitude/guildgithub.com/getpapi/papi
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 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

guild

In its own words, on Claude Code: claude-plugins-community:

Guild turns Claude Code into a self-evolving team of specialist agents for larger software tasks. It plans before execution, selects the right specialists, assembles focused context, preserves durable project memory, and improves its skills over time through evidence-based reflection. Instead of treating every request as a single long prompt, Guild breaks work into a governed workflow: clarify the goal, compose the right agent team, execute with scoped context, review the results, capture decisions, and only evolve specialists or skills when repeated evidence shows they are useful. When native agent teams are available, Guild coordinates them directly; when they are not, it falls back to sub-agents with the same planning and memory discipline. Guild is designed for projects where context, quality, and continuity matter: feature work, refactors, documentation, QA, release preparation, research-heavy implementation, and recurring workflows that benefit from reusable specialist knowledge.

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

guild As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install guild@claude-community

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.

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

Where the data comes from: how the catalog is built