Vibe Check MCP

Content

Vibe Check MCP is a maintenance-mode Model Context Protocol server for adding mentor-style plan review to agent workflows. It gives Claude tools for asking a second model to critique a goal and plan, recording recurring lessons, and checking session-specific rules before continuing complex work.

The server is designed for moments where an agent may be over-engineering, following an unsupported assumption, or preparing to take an irreversible step. It does not replace human review, tests, access control, or policy enforcement.

Source Review

• https://github.com/PV-Bhat/vibe-check-mcp-server
• https://github.com/PV-Bhat/vibe-check-mcp-server/blob/main/README.md
• https://registry.npmjs.org/%40pv-bhat%2Fvibe-check-mcp
• https://github.com/PV-Bhat/vibe-check-mcp-server/blob/main/package.json
• https://github.com/PV-Bhat/vibe-check-mcp-server/blob/main/server.json
• https://github.com/PV-Bhat/vibe-check-mcp-server/blob/main/src/index.ts
• https://github.com/PV-Bhat/vibe-check-mcp-server/blob/main/LICENSE

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm registry metadata, package metadata, MCP registry manifest, source implementation, and license file for current install commands, maintenance status, supported providers, tool schemas, transport options, and licensing.

Features

• npm package @pv-bhat/vibe-check-mcp.
• Stdio MCP server launched with npx -y @pv-bhat/vibe-check-mcp start --stdio.
• Optional HTTP transport documented upstream for clients that support it.
• vibe_check tool for goal and plan critique with optional prompt, progress, uncertainty, task context, session ID, and provider override fields.
• vibe_learn tool for recording mistakes, preferences, successes, categories, and solutions.
• update_constitution, reset_constitution, and check_constitution tools for session rules.
• Gemini, OpenAI, OpenRouter, Anthropic, and Anthropic-compatible endpoint support in the source implementation.
• MIT license.

Installation

Configure the stdio server in your MCP client:

{
  "mcpServers": {
    "vibe-check-mcp": {
      "command": "npx",
      "args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"],
      "env": {
        "GEMINI_API_KEY": ""
      }
    }
  }
}

After restarting the MCP client, ask Claude to call vibe_check before a high-risk, ambiguous, or irreversible plan, then use the critique to revise the next step.

Use Cases

• Challenge a coding agent's plan before a large refactor.
• Ask for an independent critique before running destructive commands.
• Record recurring mistakes and fixes with vibe_learn.
• Attach temporary session rules to a long agent workflow.
• Add a lightweight reflection step before ambiguous product or architecture work.
• Compare a proposed plan against uncertainties and task context.

Safety and Privacy

Vibe Check MCP should be treated as advisory. A second model can provide useful critique, but it can also misunderstand context, miss risks, or produce overconfident guidance. Continue to rely on tests, review, access controls, and human judgment for important changes.

Inputs to vibe_check and vibe_learn may include private plans, prompts, progress notes, code context, lessons learned, and session identifiers. Those values can be sent to the configured model provider, so keep secrets, customer data, regulated information, and unreleased project details out of requests unless that provider and environment are approved.

Duplicate Check

Existing MCP content includes planning, coding, browser, and automation servers, but no dedicated entry for PV-Bhat/vibe-check-mcp-server or the @pv-bhat/vibe-check-mcp package was found in content/mcp. This entry is distinct because it covers metacognitive agent oversight tools rather than a general coding, browser, or task-management MCP server.

• Source repositorygithub.com 2026-07-21T07:17:01+00:00
• Documentationgithub.com
• Submitted by oktofeesh12026-06-06