Vibecodermcp

🚀 Vibe-Coder MCP Server

A Model Context Protocol (MCP) server for structured development processes in LLM-based coding.

🚀 Quick Start

The Vibe-Coder MCP Server is designed to assist LLM in feature building by offering a structured development process. It provides various functions such as feature clarification, PRD and implementation plan generation, phased development, and task tracking.

✨ Features

Resources

• Feature details, PRDs, and implementation plans
• Progress reports and status tracking
• Phase and task details

Tools

• start_feature_clarification - Initiate the feature clarification process
• provide_clarification - Answer clarification questions about the feature
• generate_prd - Generate product requirement documents and implementation plans
• create_phase - Create a feature development phase
• add_task - Add tasks to a development phase
• update_phase_status - Update the phase status
• update_task_status - Update the task completion status
• get_next_phase_action - Get guidance for the next action
• get_document_path - Get the path of the generated document
• save_document - Save the document to a specific location

Prompt Templates

• feature-planning - A prompt template for feature development planning

📦 Installation

Use it with a compatible MCP client:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "vibe-coder-mcp": {
      "command": "/path/to/vibe-coder-mcp/build/mcp-server.js"
    }
  }
}

Debugging

Since the MCP server communicates via standard input/output, debugging can be challenging. We recommend using MCP Inspector, which is available as a package script:

npm run inspector

The Inspector will provide a URL to access the debugging tool in the browser.

💻 Usage Examples

Basic Usage

To start using the server, first install the dependencies:

npm install

Then build the server:

npm run build

For development with automatic rebuild:

npm run watch

Advanced Usage

You can customize the document storage location using the save_document tool:

{
  "featureId": "feature-123",
  "documentType": "prd",
  "filePath": "/custom/path/feature-123-prd.md"
}

To retrieve the document path, use the get_document_path tool:

{
  "featureId": "feature-123",
  "documentType": "prd"
}

📚 Documentation

Document Storage

The server includes a hybrid document storage system that:

1. Automatically generates documents (PRDs, implementation plans) and saves them as files.
2. Maintains an in-memory copy for quick access.
3. Allows clients to retrieve document paths and save documents to custom locations.

Default Storage Location

Documents are stored by default in the documents/{featureId}/ directory, with filenames based on the document type:

• documents/{featureId}/prd.md - Product requirement document
• documents/{featureId}/implementation-plan.md - Implementation plan

Custom Storage

You can use the save_document tool to save documents to a custom location.

🔧 Technical Details

The server is implemented using the advanced McpServer class from the Model Context Protocol TypeScript SDK, which simplifies the process of creating an MCP server and provides a clean API for defining resources, tools, and prompts.

import { McpServer, ResourceTemplate } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

// Create an MCP server
const server = new McpServer({
  name: "Vibe-Coder",
  version: "0.3.0"
});

// Add resources
server.resource(
  "features-list",