Vibe Coder MCP Server

Production-ready MCP server with complete agent integration, multi-transport support, and comprehensive development automation tools for AI-assisted

Local serverstdioTypeScript

What is the Vibe Coder MCP MCP server?

Production-ready MCP server with complete agent integration, multi-transport support, and comprehensive development automation tools for AI-assisted workflows. That is what the vibe coder mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Vibe Coder is an MCP (Model Context Protocol) server designed to supercharge your AI assistant (like Cursor, Cline AI, or Claude Desktop) with powerful tools for software development. It helps with research, planning, generating requirements, creating starter projects, and more!

Vibe Coder MCP integrates with MCP-compatible clients to provide the following capabilities:

Getting it running

vibe-coder-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 9 tools. What each one is for:

  • vibe-task-manager — AI-native task management with RDD methodology
  • research-manager — Deep research using Perplexity integration
  • map-codebase — Advanced codebase analysis (35+ languages)
  • curate-context — Intelligent context curation for AI development
  • generate-prd — Product requirements document generator
  • generate-user-stories — User story generator
  • generate-task-list — Task list generator
  • generate-fullstack-starter-kit — Project scaffolding tool
  • run-workflow — Multi-step workflow execution

What it needs from you

Configuration is passed through the environment: OPENROUTER_API_KEY, VIBE_PROJECT_ROOT, LOG_LEVEL, VIBE_CODER_OUTPUT_DIR, CODE_MAP_ALLOWED_DIR, VIBE_TASK_MANAGER_READ_DIR, OPENROUTER_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vibe Coder MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vibe Coder MCP's toolset — vibe-task-manager, research-manager, map-codebase and 6 more — is a fair guide to whether it matches your workflow. It is maintained by freshtechbro; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
vibe-task-managerAI-native task management with RDD methodology
research-managerDeep research using Perplexity integration
map-codebaseAdvanced codebase analysis (35+ languages)
curate-contextIntelligent context curation for AI development
generate-prdProduct requirements document generator
generate-user-storiesUser story generator
generate-task-listTask list generator
generate-fullstack-starter-kitProject scaffolding tool
run-workflowMulti-step workflow execution

How to install the Vibe Coder MCP MCP server

{
  "mcpServers": {
    "vibe-coder": {
      "command": "npx",
      "args": ["-y", "vibe-coder-mcp"],
      "env": {
        "OPENROUTER_API_KEY": "your-value",
        "VIBE_PROJECT_ROOT": "your-value",
        "LOG_LEVEL": "your-value",
        "VIBE_CODER_OUTPUT_DIR": "your-value",
        "CODE_MAP_ALLOWED_DIR": "your-value",
        "VIBE_TASK_MANAGER_READ_DIR": "your-value",
        "OPENROUTER_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
OPENROUTER_API_KEYCredential the server authenticates with.Yes
VIBE_PROJECT_ROOTConfiguration value read at startup.Optional
LOG_LEVELConfiguration value read at startup.Optional
VIBE_CODER_OUTPUT_DIRFilesystem location the server is allowed to use.Optional
CODE_MAP_ALLOWED_DIRFilesystem location the server is allowed to use.Optional
VIBE_TASK_MANAGER_READ_DIRFilesystem location the server is allowed to use.Optional
OPENROUTER_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Vibe Coder MCP to vibe-task-manager.
  • Use Vibe Coder MCP to research-manager.
  • Use Vibe Coder MCP to map-codebase.

Frequently asked questions

It connects Vibe Coder MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (vibe-task-manager, research-manager, map-codebase, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vibe Coder MCP directly.