conductor vs PAPI: Persistent Adaptive Project Intelligence
conductor is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑29.
conductor is a plugin bundle for AI coding tools published by Bryan Lackey. No marketplace we read lists it any more. 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-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace lackeyjb/claude-conductor | Removed on 2026-10-29 Version: 1.2.0 Forks (GitHub): 2 Stars (GitHub): 15 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 | conductorno longer listed · | PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 15 | 11 |
| Forks (GitHub) (differs) | 2 | 0 |
| 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) | 4 | Not published |
| Parts of the bundle (differs) | 16 | 15 |
| Licence (differs) | Apache-2.0 | Elastic-2.0 |
| Repository (differs) | github.com/lackeyjb/claude-conductor | github.com/getpapi/papi |
| Changes in the last 7 days (differs) | 4 | 1 |
| First seen (differs) | 2026-10-26 | 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. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of conductor
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Multi-agent development harness for Claude Code. Your AI has speed; we give it direction — through living specs and focused specialist agents.
-
Turn Claude Code into an autonomous software development team — 16 specialized agents, documentation-first pipeline, TDD slices in parallel waves, and 9 quality gates.
-
Story Driven Development workflow for Claude Code. Keeps your documentation and code in sync via status tracking and git-diff-based prompts.
-
Accelerates software delivery by automating SDLC stages inside Claude Code — Claude facilitates writing specs and designing architecture, then autonomously builds implementation…
-
Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and OKF knowledge bundles.
-
Test-Driven Generation plugin for Claude Code
What each says it does
conductor
Context-Driven Development framework for Claude Code
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
How to run each
conductor
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PAPI: Persistent Adaptive Project Intelligence As a remote MCP server
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: conductor · 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.