🧠 Vibe Check MCP

Also find Vibecheck on: mcpservers.org, Glama.ai, mcp.so

Your AI's inner rubber duck when it can't rubber duck itself.

What is Vibe Check?

In the "vibe coding" era, AI agents now have incredible capabilities, but the question has now moved:

from

"Can my AI agent really do this complex task?"

to

"Can my AI agent understand that I want to write a simple program, not an infrastructure for a multi-billion dollar tech company?"

It provides the essential "Hold up... this ain't it" moment that AI agents don't currently have: a built in self-correcting oversight layer. It's the definitive Vibe Coder's sanity check MCP server:

• Prevent cascading errors in AI workflows by implementing strategic pattern interrupts.
• Uses tool call "Vibe Check" with LearnLM 1.5 Pro (Gemini API), fine-tuned for pedagogy and metacognition to enhance complex workflow strategy, and prevents tunnel vision errors.
• Implements "Vibe Distill" to encourage plan simplification, prevent over-engineering solutions, and minimize contextual drift in agents.
• Self-improving feedback loops: Agents can log mistakes into "Vibe Learn" to improve semantic recall and help the oversight AI target patterns over time.

TLDR; Implement an agent fine-tuned to stop your agent and make it reconsider before it confidently implements something wrong.

The Problem: Pattern Inertia

In the vibe coding movement, we're all using LLMs to generate, refactor, and debug our code. But these models have a critical flaw: once they start down a reasoning path, they'll keep going even when the path is clearly wrong.

You: "Parse this CSV file"

AI: "First, let's implement a custom lexer/parser combination that can handle arbitrary 
     CSV dialects with an extensible architecture for future file formats..."

You: *stares at 200 lines of code when you just needed to read 10 rows*

This pattern inertia leads to:

• 🔄 Tunnel vision: Your agent gets stuck in one approach, unable to see alternatives
• 📈 Scope creep: Simple tasks gradually evolve into enterprise-scale solutions
• 🔌 Overengineering: Adding layers of abstraction to problems that don't need them
• ❓ Misalignment: Solving an adjacent but different problem than the one you asked for

Features: Metacognitive Oversight Tools

Vibe Check adds a metacognitive layer to your agent workflows with three integrated tools:

🛑 vibe_check

Pattern interrupt mechanism that breaks tunnel vision with metacognitive questioning:

vibe_check({
  "phase": "planning",           // planning, implementation, or review
  "userRequest": "...",          // FULL original user request 
  "plan": "...",                 // Current plan or thinking
  "confidence": 0.7              // Optional: 0-1 confidence level
})

⚓ vibe_distill

Meta-thinking anchor point that recalibrates complex workflows:

vibe_distill({
  "plan": "...",                 // Detailed plan to simplify
  "userRequest": "..."           // FULL original user request
})

🔄 vibe_learn

Self-improving feedback loop that builds pattern recognition over time:

vibe_learn({
  "mistake": "...",              // One-sentence description of mistake
  "category": "...",             // From standard categories
  "solution": "..."              // How it was corrected
})

Vibe Check in Action

Before Vibe Check:

Claude assumes the meaning of MCP despite ambiguity, leading to all subsequent steps having this wrong assumption

After Vibe Check:

Vibe Check MCP is called, and points out the ambiguity, which forces Claude to acknowledge this lack of information and proactively address it

Installation & Setup

Installing via Smithery

To install vibe-check-mcp-server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @PV-Bhat/vibe-check-mcp-server --client claude

Manual Installation via npm (Recommended)

# Clone the repo
git clone https://github.com/PV-Bhat/vibe-check-mcp-server.git
cd vibe-check-mcp-server

# Install dependencies
npm install

# Build the project
npm run build

# Start the server
npm run start

Integration with Claude

Add to your claude_desktop_config.json:

"vibe-check": {
  "command": "node",
  "args": [
    "/path/to/vibe-check-mcp/build/index.js"
  ],
  "env": {
    "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY"
  }
}

Environment Configuration

Create a .env file in the project root:

GEMINI_API_KEY=your_gemini_api_key_here

Agent Prompting Guide

For effective pattern interrupts, include these instructions in your system prompt:

As an autonomous agent, you will:

1. Treat vibe_check as a critical pattern interrupt mechanism
2. ALWAYS include the complete user request with each call
3. Specify the current phase (planning/implementation/review)
4. Use vibe_distill as a recalibration anchor when complexity increases
5. Build the feedback loop with vibe_learn to record resolved issues

When to Use Each Tool

API Reference

See the Technical Reference for complete API documentation.

Architecture

Vibe Check in Action (Continued)

Documentation

Contributing

We welcome contributions to Vibe Check! Whether it's bug fixes, feature additions, or just improving documentation, check out our Contributing Guidelines to get started.

License

MIT