VibeCoderMCP
About
Guides LLMs through structured software development workflows with feature clarification, PRD generation, and phase-based tracking using a hybrid document storage system.
Details
- Author
- crazyrabbitltc
- Repository
- crazyrabbitLTC/mcp-vibecoder
- GitHub stars
- 7
- Downloads
- 284
- Categories
- Developer Tools, Automation, Project Management, Productivity, Design, Workplace, File Management, AI, Frontend, Infrastructure, Other
Jump to
- 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
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
VibeCoderMCPCommand (node, npx, python, etc.)/path/to/vibe-coder-mcp/build/mcp-server.jsPlease refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
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"
}
}
}
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.
- 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
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"vibecodermcp": {
"cwd": "optional",
"env": {},
"args": [],
"shell": false,
"command": "/path/to/vibe-coder-mcp/build/mcp-server.js"
}
}
}Linux
{
"cwd": "optional",
"env": [],
"args": [],
"shell": false,
"command": "/path/to/vibe-coder-mcp/build/mcp-server.js"
}Macos
{
"cwd": "optional",
"env": [],
"args": [],
"shell": false,
"command": "/path/to/vibe-coder-mcp/build/mcp-server.js"
}Windows
{
"cwd": "optional",
"env": [],
"args": [],
"shell": false,
"command": "/path/to/vibe-coder-mcp/build/mcp-server.js"
}A Model Context Protocol server that implements a structured development workflow for LLM-based coding.
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
- Feature details, PRDs, and implementation plans
- Progress reports and status tracking
- Phase and task details
- 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
- feature-planning- A prompt template for planning feature development
The server includes a hybrid document storage system that:
- Automatically saves generated documents (PRDs, implementation plans) to files
- Maintains an in-memory copy for quick access
- Allows clients to retrieve document paths and save to custom locations
Documents are stored in thedocuments/{featureId}/directory by default, with filenames based on document type:
- documents/{featureId}/prd.md- Product Requirements Document
- documents/{featureId}/implementation-plan.md- Implementation Plan
You can use thesave_documenttool to save documents to custom locations:
{ "featureId": "feature-123", "documentType": "prd", "filePath": "/custom/path/feature-123-prd.md" }
To get the path of a document, use theget_document_pathtool:
{ "featureId": "feature-123", "documentType": "prd" }
This returns both the path and whether the document has been saved to disk.
On MacOS:~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows:%APPDATA%/Claude/claude_desktop_config.json
{ "mcpServers": { "vibe-coder-mcp": { "command": "/path/to/vibe-coder-mcp/build/mcp-server.js" } } }
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using theMCP Inspector, which is available as a package script:
The Inspector will provide a URL to access debugging tools in your browser.
This server is implemented using the high-levelMcpServerclass from the Model Context Protocol TypeScript SDK, which simplifies the process of creating MCP servers by providing 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 a resource server.resource( "features-list", "features://list", async (uri) => ({ / ... / }) ); // Add a tool server.tool( "start_feature_clarification", { / parameters schema / }, async (params) => ({ / ... / }) ); // Add a prompt server.prompt( "feature-planning", { / parameters schema / }, (params) => ({ / ... / }) ); // Start the server const transport = new StdioServerTransport(); await server.connect(transport);
The Vibe-Coder MCP server is designed to guide the development process through the following steps:
- Feature Clarification: Start by gathering requirements and understanding the feature's purpose, target users, and constraints
- Documentation: Generate a PRD and implementation plan based on the clarified requirements
- Phased Development: Break down the implementation into logical phases with clear tasks
- Progress Tracking: Monitor the completion of tasks and phases to guide development
- Completion: Verify that all requirements have been implemented and the feature is ready for use
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
An MCP server for initial app planning and creating a good starting point for an app.
An AI-powered server that facilitates feature discussions between developers and AI, acting as a lead developer to guide implementation and architectural decisions.
Inspectable coding sessions and workspace orchestration for software projects.
A conversation-driven development framework for rapid MVP and POC creation.
Connect bugAgent to any MCP-compatible AI client. File, classify, and manage bugs, feature requests, and more directly from your AI coding assistant. No context switching, no copy-paste — just describe the issue and bugAgent handles the rest.
his repository contains a fully functional MCP (Model Context Protocol) server, providing solutions for Constraint Satisfaction Problems (CSP) and Linear Programming (LP). It is based on the gurddy package and supports solving a variety of classic problems.
Execute any LLM-generated code in the YepCode secure and scalable sandbox environment and create your own MCP tools using JavaScript or Python, with full support for NPM and PyPI packages
Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.
An engineering governance and safety control plane for AI coding agents to enforce strict SDLC discipline, quality gates, and security branch protections.
MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
