一个模式背景协议服务器,用于执行基于LLM的编码结构化开发工作流程.

□ 概览

MCP服务器通过提供:

• 结构化的特征澄清过程和有指导的问题
• PRD和执行计划的制定
• 分阶段进行任务跟踪
• 进展跟踪和现况报告
• 文件储存和检索能力

□ 特性

资源

• 具体内容、项目内容和执行计划
• 进度报告和现状跟踪
• 阶段和任务细节

QQ 工具 [[T0] - 开始特征澄清程序

• [[T1]-回答关于某一特征的澄清问题
• [[T2] – – 产生产品要求文件和实施计划
• create_phase - 为特性创建开发阶段
• add_task - 在开发阶段添加任务
• [[T5] - 更新一个阶段的状况
• [[T6]-更新一项任务的完成情况
• get_next_phase_action - 获得下一步行动的指导
• get_document_path - 获取生成的文档的路径

Vibe-Coder MCP Server

A Model Context Protocol server that implements a structured development workflow for LLM-based coding.

Overview

This MCP server helps LLMs build features in an organized, clean, and safe manner by providing:

• A structured feature clarification process with guided questions
• PRD and implementation plan generation
• Phased development with task tracking
• Progress tracking and status reporting
• Document storage and retrieval capabilities

Features

Resources

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

Tools

• start_feature_clarification - Begin the feature clarification process
• provide_clarification - Answer clarification questions about a feature
• generate_prd - Generate a Product Requirements Document and implementation plan
• create_phase - Create a development phase for a feature
• add_task - Add tasks to a development phase
• update_phase_status - Update the status of a phase
• update_task_status - Update the completion status of a task
• get_next_phase_action - Get guidance on what to do next
• get_document_path - Get the path of a generated document
• save_document - Save a document to a specific location

Prompts

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

Document Storage

The server includes a hybrid document storage system that:

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

Default Storage Location

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

• documents/{featureId}/prd.md - Product Requirements Document
• documents/{featureId}/implementation-plan.md - Implementation Plan

Custom Storage

You can use the save_document tool to save documents to custom locations:

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

Path Retrieval

To get the path of a document, use the get_document_path tool:

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

This returns both the path and whether the document has been saved to disk.

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

To use with compatible MCP clients:

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