LLMベースのコーディングのための構造開発ワークフローを実装するモデルコンテキストプロトコルサーバー。

概要

このMCPサーバーは、LLMが組織化された、清潔で安全な方法で機能を構築するのに役立ちます。

• ガイドされた質問の構造化された特徴の明確化プロセス
• PRDと実装計画の生成
• タスクトラッキングによるフェーズド開発
• 進捗追跡とステータスレポート
• ドキュメントストレージと検索機能

##特徴

リソース

• 特徴の細部、PRDsおよび実施計画
• 進捗レポートとステータストラッキング
• フェーズとタスクの詳細

ツール

• [start_feature_clarification - 機能の明確化プロセスを開始
• provide_clarification - 機能に関する明確化の質問に答える
• [generate_prd - 製品の要件文書と実装計画の生成
• [create_phase - 機能の開発フェーズを作成する
• [add_task - 開発フェーズにタスクを追加する
• update_phase_status - フェーズのステータスを更新する
• [update_task_status - タスクの完了状況を更新する
• [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