LabscoMCP early access ↗
Zenobia000MCP SERVER · OFFICIAL PROJECT

VibeCoding System

Six MCP services that walk a project from clarifying questions to PRD, code, tests and deployment.

by Zenobia000 ↗Reasoning Scaffolds & Agent Workflow Engines✓ Official

LABSCO SUMMARY

The questions come before the code.

Most code-generation tools start at "write me a"; this one starts by asking seven structured questions and turning the answers into a PRD the later stages read from. That ordering is the whole point — the phase folders mean the plan is a file the implementation stage can consult, not context that scrolled away. Setup is path-sensitive: absolute paths and a rebuild after every change.

What it is

VibeCoding turns development into a guided conversation: six specialised MCP services carry a project through clarification, design, implementation, testing and deployment, each with short @vibe commands and a longer explicit form.

What you get

  • Context Manager — start-clarification opens a project with structured questions, provide-clarification answers them one at a time, generate-prd writes the product requirements document, generate-impl-plan turns it into a technical plan
  • Code Generator — generate-code, code-review, refactor-code
  • Dependency Tracker — analyze-dependencies, security-scan, update-dependencies
  • Test Validator — run-tests, validate-coverage, performance-test
  • Doc Generator — generate-docs, create-api-docs, generate-changelog
  • Deployment Manager — deploy-service, setup-monitoring, rollback-deployment
  • Project scaffolding creates five phase folders — 0_discovery/, 1_design/, 2_implementation/, 3_validation/, 4_deployment/ — plus a knowledge base, so artefacts land where the next stage expects them
  • Prompts under .vibecoding/prompts/ load according to the current phase, so guidance changes as the project moves

Requirements

Node.js >= 18.0.0 and npm >= 8.0.0, on Windows 10/11, macOS or Linux, with at least 4GB RAM. Clone the repo, npm install && npm run build, then verify with npm run vibecoding status and npm run test:prompts. Register the built service under mcpServers in Cursor's settings.json or claude_desktop_config.json using an absolute path to dist/vibe-services/context-manager/index.js — relative paths are the most common failure. Cursor needs no API key; other setups can supply OPENAI_API_KEY, ANTHROPIC_API_KEY or GEMINI_API_KEY. MIT.

Setup effort

Build from source — git clone https://github.com/Zenobia000/vibeCoding-mcp.git

See installation options