Vibe Coding Control vs PAPI: Persistent Adaptive Project Intelligence
Vibe Coding Control is an MCP server published by OMNOM-111. Marketplaces we read that list it: 1 (Official MCP Registry). 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-28. 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 |   Vibe Coding Control |  PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
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 | Vibe Coding Control | PAPI: Persistent Adaptive Project Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 11 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-15 (worse) | 2026-10-16 (better) |
| Where it runs (differs) | Remote server (vibecodingcontrol.com/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 15 |
| Licence (differs) | Not stated | Elastic-2.0 |
| Repository (differs) | github.com/omnom-111/vcc-remote | github.com/getpapi/papi |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 34 h ago, requires a key | Not responding since 2026-10-23 |
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
Vibe Coding Control
Your VCC projects, tasks, AI development history and owner decisions. Sign in with your VCC account.
PAPI: Persistent Adaptive Project Intelligence
Adaptive plan/build/review cycles for AI coding assistants, persisted across sessions.
How to run each
Vibe Coding Control As a remote MCP server
claude mcp add --transport http vcc-remote https://vibecodingcontrol.com/mcpPAPI: 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 the endpoint of Vibe Coding Control responded at the last daily 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: Vibe Coding Control · What it can do: PAPI: Persistent Adaptive Project Intelligence · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.