vibe-check-mcp-server MCP — Anwendungsfälle, Installieren & Live-Demo

Name: vibe-check-mcp-server MCP Server
Author: PV-Bhat

Warum nutzen

Hauptfunktionen

vibe_check tool interrupts with pushback before irreversible actions
vibe_learn captures per-session lessons for in-context improvement
Constitution tools define per-session rules the agent must follow
Pure prompt-wrapping — no data leaves your chosen LLM provider

Live-Demo

In der Praxis

vibe-check.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "vibe-check": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-check-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "vibe-check": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-check-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "vibe-check": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-check-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "vibe-check": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-check-mcp-server"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "vibe-check",
      "command": "npx",
      "args": [
        "-y",
        "vibe-check-mcp-server"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "vibe-check": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "vibe-check-mcp-server"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add vibe-check -- npx -y vibe-check-mcp-server

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: vibe-check-mcp-server

Sanity-check a plan before a destructive action with vibe-check

👤 Anyone running agents with write access ⏱ ~10 min beginner

Wann einsetzen: The agent is about to delete files, run a migration, or deploy — you want a second opinion.

Ablauf

Invoke vibe_check on the plan

Before running the migration, call vibe_check on this plan: [paste]. What could go wrong?✓ Kopiert

→ Pushback list: unchecked assumptions, missing rollback, scope creep
Resolve or ignore each concern explicitly

Address each concern — either mitigate or explicitly dismiss as out of scope.✓ Kopiert

→ Annotated plan ready to run

Ergebnis: Fewer 'oh no' moments after destructive actions.

Fallstricke

Agent dismisses all concerns rubber-stamp style — Require the agent to restate each concern and the specific mitigation

Kombinieren mit: sequentialthinking-tools

Enforce session rules with vibe-check's constitution

👤 Teams sharing agent workflows ⏱ ~10 min intermediate

Wann einsetzen: You want certain rules (never push to main, always write tests first) enforced across a session.

Ablauf

Set the constitution

Use update_constitution to set these rules for this session: [list]. Enforce via CPI on every tool call that could violate them.✓ Kopiert

→ Rules acknowledged; subsequent violations get interrupted
Inspect when in doubt

Call check_constitution to see what's currently in effect.✓ Kopiert

→ Current rules list

Ergebnis: Consistent agent behavior within a session without repeating rules every message.

Capture lessons from agent mistakes with vibe_learn

👤 Agent developers iterating on prompts ⏱ ~5 min beginner

Wann einsetzen: The agent made a classic mistake; you want it not to repeat.

Ablauf

Log the lesson

Call vibe_learn with: mistake='deleted prod table without snapshot', lesson='always take a snapshot before DDL on prod'.✓ Kopiert

→ Lesson stored for the session
Rely on it later

(later in same session) Attempt a DDL — vibe_check surfaces the stored lesson✓ Kopiert

→ Interrupt with the relevant past lesson

Ergebnis: In-session memory of 'don't do that again' without prompt engineering.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

vibe-check + sequentialthinking-tools

Plan + pushback loop

Plan with sequentialthinking_tools, then call vibe_check on the plan before executing step 1.✓ Kopiert

vibe-check + overture

Visual plan + vibe-check layer

After Overture produces the plan graph, run vibe_check on it and surface concerns as annotations.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
vibe_check	plan: str, context?: str	Before any non-trivial or irreversible action	1 LLM call via your configured provider
vibe_learn	mistake: str, lesson: str	Immediately after a mistake, while fresh	0
update_constitution	rules: str[]	Session start or policy change	0
check_constitution		Debug unexpected interrupts	0
reset_constitution		Start fresh	0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: Uses your chosen LLM's quota
Tokens pro Aufruf: 500-3000 for vibe_check
Kosten in €: LLM token cost only
Tipp: Only vibe_check on substantive plans — skipping it on trivial edits saves tokens

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: LLM API key in env (OPENAI_API_KEY, ANTHROPIC_API_KEY, etc.)

Datenabfluss: Only to your configured LLM provider

Fehlerbehebung

Häufige Fehler und Lösungen

vibe_check returns empty concerns

Plan input was too vague — include concrete steps and side effects

Agent ignores vibe_check output

Make the system prompt require addressing each concern before proceeding

npx cannot find @pv-bhat/vibe-check-mcp

The published scope is @pv-bhat; pin latest explicitly: npx -y @pv-bhat/vibe-check-mcp@latest

Alternativen

vibe-check-mcp-server vs. andere

Alternative	Wann stattdessen	Kompromiss
sequentialthinking-tools	You want planning, not pushback	Different shape — no adversarial second model
overture	You want visual gating instead of text pushback	Heavier setup

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen