vibe-cartographer vs PreVibe
vibe-cartographer is a plugin bundle for AI coding tools published by estevanhernandez-stack-ed. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). PreVibe is an MCP server published by previbe.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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-cartographer |  PreVibe |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: e9a8f3a Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.4.1 No figure published 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-cartographer | PreVibe |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (previbe.io/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/estevanhernandez-stack-ed/vibe-cartographer | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 16 h ago, requires authentication |
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-cartographer
Vibe Cartographer turns the vibe-coding hype into a structured workflow. Eight commands walk you from idea spark to shipped app: a flipped-interaction onboarding (/onboard), a scope brainstorm (/scope), a PRD interview (/prd), a tech spec grounded in your architecture (/spec), a dependency-aware build checklist (/checklist), an autonomous-or-step-by-step build loop (/build), an optional polish pass (/iterate), and a real retrospective (/reflect). The agent picks up a unified builder profile at ~/.claude/profiles/builder.json so persona, pacing, and stack preferences carry across projects and across other 626Labs plugins. Three Level-3.5 self-evolution commands round it out: /evolve (the plugin reads its own logs and proposes improvements), /vitals (self-diagnostic health check), /friction (real-time friction capture for future evolve cycles).
PreVibe
Validate your SaaS idea with market research before you build it.
How to run each
vibe-cartographer As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibe-cartographer@claude-communityPreVibe As a remote MCP server
claude mcp add --transport http previbe https://previbe.io/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PreVibe 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: vibe-cartographer · What it can do: PreVibe · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.