Vibe-Coder

Vibe Coder MCP Server is an expressive AI-assisted development hub designed to augment your AI assistant with a suite of software-engineering focused tools. It exposes a collection of MCP-compatible capabilities such as generating product requirements, creating starter code, mapping codebases, and organizing tasks and workflows. After integration with an MCP client (e.g., Claude Desktop, Cursor, or Cline AI), you can access tools like task management, research, codebase analysis, context curation, PRD and user story generation, and full-stack starter kit creation. The server supports both a CLI/REPL experience and interactive chat-style sessions, with progress indicators and structured outputs to help you manage multi-step development tasks. The tools are designed to work across languages and technologies, enabling rapid planning, exploration, and scaffolding for software projects.

Once configured in your MCP client, you can invoke tools such as vibe-task-manager, research-manager, map-codebase, curate-context, generate-prd, generate-user-stories, generate-task-list, generate-fullstack-starter-kit, and run-workflow. Each tool is tailored to produce concrete artifacts (plans, requirements, code scaffolds, and task lists) and to integrate with your project context to deliver coherent results. The interactive REPL and JSON log filtering features help maintain clarity when juggling long-running jobs or multi-turn conversations.

Prerequisites:

• Node.js version 20.0.0 or newer
• npm (comes with Node.js) or npm-compatible tooling

Installation options:

1. Global installation (recommended for CLI access):

npm install -g vibe-coder-mcp@latest

2. Quick run with npx (no installation needed):

npx vibe-coder-mcp@latest

3. Local project installation (if you prefer to keep it project-scoped):

npm install vibe-coder-mcp
npx vibe-coder-mcp "map the codebase structure"

Configuration steps:

• If using the MCP client integration, set the server to run with the npx command (as shown above) and provide the required environment variables (OPENROUTER_API_KEY, VIBE_PROJECT_ROOT, etc.).
• Ensure your project root path is accessible and that the OpenRouter API key is valid.
• Start the MCP server via your chosen method (global CLI, npx, or via your MCP client configuration).

Tips and common considerations:

• Ensure OpenRouter API key and project root are correctly configured in the environment to enable full functionality.
• If you see low-confidence matches, the system can prompt for user confirmation to avoid undesired actions.
• Use the interactive REPL mode for exploratory planning and iterative refinement of prompts and plans.
• For Claude Desktop integration, you can configure the provided JSON example to wire the MCP server into your Claude setup.
• If running behind a proxy or VPN, ensure network access to required OpenRouter endpoints and npm registry for updates.