MCP Vibecoder MCP Server

MCP Vibecoder becomes available to MCP clients through the mcp vibecoder mcp server. A custom MCP for vibecoding.

What MCP Vibecoder does

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:

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• 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
• Resources — The Resources tool exposed by this server
• Tools — The Tools tool exposed by this server
• Prompts — The Prompts tool exposed by this server
• Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Installing the mcp vibecoder mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. MCP Vibecoder sits in that group, and the shape of its toolset — start_feature_clarification, provide_clarification, generate_prd among others — tells you what it is really for. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use MCP Vibecoder.
• Maintained by crazyrabbitLTC, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp vibecoder mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.