The Vibe-Coder MCP Server implements the Model Context Protocol to provide a structured workflow for LLM-based coding. It guides the development process through feature clarification, PRD generation, phased implementation, and progress tracking, helping to organize coding tasks in a systematic way.
To install and set up the Vibe-Coder MCP Server with compatible MCP clients:
Configure your client by updating the configuration file at:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%/Claude/claude_desktop_config.json
Add the following configuration:
{
"mcpServers": {
"vibe-coder-mcp": {
"command": "/path/to/vibe-coder-mcp/build/mcp-server.js"
}
}
}
Replace /path/to/vibe-coder-mcp
with the actual path to where you've installed the server.
Since MCP servers communicate over stdio, you can use the MCP Inspector for debugging:
npm run inspector
This will provide a URL to access debugging tools in your browser.
The MCP server manages several resources:
The server guides you through a structured development process:
Begin with feature clarification:
{
"featureId": "feature-123",
"featureName": "User Authentication",
"initialDescription": "Implement a secure login system"
}
Generate a PRD and implementation plan:
{
"featureId": "feature-123"
}
Create a development phase:
{
"featureId": "feature-123",
"phaseName": "Setup Database Schema",
"phaseDescription": "Create tables and relationships for user data"
}
Add tasks to phases:
{
"featureId": "feature-123",
"phaseId": "phase-456",
"taskName": "Create users table",
"taskDescription": "Define user table with appropriate fields"
}
Update progress:
{
"featureId": "feature-123",
"phaseId": "phase-456",
"status": "completed"
}
{
"featureId": "feature-123",
"phaseId": "phase-456",
"taskId": "task-789",
"status": "completed"
}
Get guidance on next steps:
{
"featureId": "feature-123"
}
The server includes document storage capabilities for PRDs and implementation plans.
Documents are automatically stored in:
documents/{featureId}/prd.md
- Product Requirements Documentdocuments/{featureId}/implementation-plan.md
- Implementation PlanTo get the path of a document:
{
"featureId": "feature-123",
"documentType": "prd"
}
Save documents to custom locations:
{
"featureId": "feature-123",
"documentType": "prd",
"filePath": "/custom/path/feature-123-prd.md"
}
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.