Vibe-Coder MCP Server

What is Vibe-Coder MCP Server?

Vibe-Coder MCP Server is a Model Context Protocol server that implements a structured development workflow for LLM-based coding. It helps LLMs build features in an organized, clean, and safe manner by providing clarification, documentation, task tracking, and document storage.

How to use Vibe-Coder MCP Server?

Install dependencies with npm install, build the server with npm run build, then configure it in your MCP client’s config file (e.g., claude_desktop_config.json on MacOS or Windows). Use the provided tools and prompts to guide feature development.

Key features of Vibe-Coder MCP Server

• Structured feature clarification with guided questions
• PRD and implementation plan generation
• Phased development with task tracking
• Progress tracking and status reporting
• Hybrid document storage (disk + in‑memory)
• Tools for clarifying, documenting, phasing, and tracking features

Use cases of Vibe-Coder MCP Server

• Developing a new feature from requirements gathering to completion
• Iterating on an existing codebase with structured planning and documentation
• Breaking a large feature into manageable phases and tasks
• Tracking progress across multiple development steps
• Automating the generation of PRDs and implementation plans

FAQ from Vibe-Coder MCP Server

How do I install and configure the Vibe-Coder MCP Server?

Install dependencies with npm install, build with npm run build, then add the server configuration to your MCP client’s JSON config file (e.g., claude_desktop_config.json). The server runs over stdio.

How does document storage work?

Documents are saved automatically to documents/{featureId}/ by default, with filenames like prd.md and implementation-plan.md. You can also use the save_document tool to write to a custom path, and get_document_path to retrieve the current path and save status.

What tools does the server provide?

Tools include start_feature_clarification, provide_clarification, generate_prd, create_phase, add_task, update_phase_status, update_task_status, get_next_phase_action, save_document, and get_document_path.

What is the development workflow?

The workflow follows five steps: 1) feature clarification, 2) documentation (PRD and implementation plan), 3) phased development with tasks, 4) progress tracking, and 5) completion verification.

How can I debug the server?

Use the MCP Inspector by running npm run inspector, which provides a URL to debugging tools in your browser. The server communicates over stdio, so the Inspector is the recommended debugging approach.