Vibe-Coder MCP Server logo

Vibe-Coder MCP Server

by crazyrabbitLTC

The Vibe-Coder MCP Server is a Model Context Protocol server designed to provide a structured development workflow for LLM-based coding. It helps LLMs build features in an organized, clean, and safe manner.

View on GitHub

Last updated: N/A

What is Vibe-Coder MCP Server?

The Vibe-Coder MCP server provides a structured environment for LLMs to develop features, including feature clarification, PRD generation, phased development, progress tracking, and document storage.

How to use Vibe-Coder MCP Server?

To use the server, integrate it with a compatible MCP client by configuring the client with the server's command path. Use the provided tools to initiate feature clarification, generate documentation, create development phases, add tasks, update statuses, and retrieve documents. Refer to the README for installation and debugging instructions.

Key features of Vibe-Coder MCP Server

  • Structured feature clarification process

  • PRD and implementation plan generation

  • Phased development with task tracking

  • Progress tracking and status reporting

  • Document storage and retrieval capabilities

  • Tools for managing feature development lifecycle

  • Prompts for feature planning

Use cases of Vibe-Coder MCP Server

  • Guiding LLMs in building new software features

  • Automating the generation of product requirements documents

  • Managing the development process of LLM-based applications

  • Tracking the progress of feature implementation

  • Providing a structured workflow for collaborative coding with LLMs

FAQ from Vibe-Coder MCP Server

Where are documents stored by default?

Documents are stored in the documents/{featureId}/ directory, with filenames like prd.md and implementation-plan.md.

Can I save documents to a custom location?

Yes, you can use the save_document tool to specify a custom file path.

How do I get the path of a generated document?

Use the get_document_path tool, providing the feature ID and document type.

How do I debug the MCP server?

Use the MCP Inspector, which can be launched with npm run inspector.

What is the overall workflow?

The workflow includes feature clarification, documentation generation, phased development, progress tracking, and completion verification.