map-codebaseLABSCO SUMMARY
Output goes to disk, which is what makes it a workflow.
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.
What it is
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.
What you get
research— deep research through Perplexity Sonar, returning summaries and sourcesprd-generator,user-stories-generator,task-list-generator— the planning documents, generated in sequence, withrules-generatorfor project-specific development rulesfullstack-starter-kit-generator— project scaffoldingmap-codebase— codebase analysis spanning 35+ languagescurate-context— assembles the relevant context for a development task instead of dumping the repositoryvibe-task-manager— task management using RDD methodologyrun-workflow— multi-step workflow execution- The same tools from a terminal:
vibe "create a PRD for a todo app",vibe --interactivefor a chat-style REPL with session persistence,vibe --setupfor the wizard
Requirements
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.
Setup effort
One command plus a key — npm install -g vibe-coder-mcp@latest, then supply credentials
USE CASES
01
Going from an idea to a task list
Research the space, generate the requirements document, derive user stories, and turn those into tasks — each step written to the output directory.
02
Understanding a repository you inherited
Map the codebase, then curate the subset of it that is relevant to the change you are about to make.
03
Starting a new project from a scaffold
Generate a full-stack starter kit rather than assembling boilerplate by hand.
10 tools
Listed in project docs. Your client may show a different list.
curate-contextresearchrules-generatorprd-generatoruser-stories-generatortask-list-generatorfullstack-starter-kit-generatorrun-workflowvibe-task-managerBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
OPENROUTER_API_KEY in your environment
Where it runs
All 6 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g vibe-coder-mcp@latestMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"vibe-coder-mcp": {
"command": "npx",
"args": [
"vibe-coder-mcp"
],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>",
"VIBE_PROJECT_ROOT": "<YOUR_VIBE_PROJECT_ROOT>",
"LOG_LEVEL": "info",
"NODE_ENV": "production"
}
}
}
}Cursor, Windsurf
JSON
{
"mcpServers": {
"vibe-coder-mcp": {
"command": "npx",
"args": [
"vibe-coder-mcp"
],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"vibe-coder-mcp": {
"command": "npx",
"args": [
"vibe-coder-mcp"
],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>"
}
}
}
}Any MCP client — global install
ANY MCP CLIENT — GLOBAL INSTALL · JSON
{
"mcpServers": {
"vibe-coder-mcp": {
"command": "vibe",
"args": [],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>",
"VIBE_PROJECT_ROOT": "<YOUR_VIBE_PROJECT_ROOT>"
}
}
}
}Any MCP client — node
ANY MCP CLIENT — NODE · JSON
{
"mcpServers": {
"vibe-coder-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_NODE_MODULES>/vibe-coder-mcp/build/index.js"
]
}
}
}
