A model can already write you a PRD in a chat window; the difference here is that the artefacts are written into the project, one feeding the next — research into requirements, requirements into user stories, stories into a task list the task manager then tracks. The codebase map and context curation exist for the reverse direction: understanding a project well enough to plan against it.
A planning and analysis server for software work. It is both an MCP server for Cursor, Cline and Claude Desktop and a `vibe` command with an interactive REPL, and both drive the same tools against the project directory you point it at.
- `research-manager` — deep research through a Perplexity integration
- `generate-prd`, `generate-user-stories`, `generate-task-list` — the planning documents, generated in sequence
- `generate-fullstack-starter-kit` — project scaffolding
- `map-codebase` — codebase analysis spanning 35+ languages
- `curate-context` — assembles the relevant context for a development task instead of dumping the repository
- `vibe-task-manager` — task management using RDD methodology
- `run-workflow` — multi-step workflow execution
- The same tools from a terminal: `vibe "create a PRD for a todo app"`, `vibe --interactive` for a chat-style REPL with session persistence, `vibe --setup` for the wizard
Node.js 20.0.0 or newer, and an OpenRouter API key in `OPENROUTER_API_KEY` — that one is required, not optional, and the setup wizard exists mainly to configure it. `VIBE_PROJECT_ROOT` tells MCP clients which project to work on; the CLI detects it automatically. Generated files land in `VIBE_CODER_OUTPUT_DIR`, defaulting to `./VibeCoderOutput/`. Install with `npm install -g vibe-coder-mcp@latest` or run it through `npx`; the package is `vibe-coder-mcp`.
One command plus a key — npm install -g vibe-coder-mcp@latest, then supply credentials