vibecheck0.3.0
AI Agent Setup

Other MCP clients

Claude Desktop, Windsurf, and the universal config block.

Every MCP client that speaks stdio accepts the same server definition. If your client isn't Claude Code or Cursor, use the block below.

The universal config

{
  "mcpServers": {
    "vibe-check": {
      "command": "npx",
      "args": ["-y", "@wcgw/vibe-check-mcp@0.3.0", "connect"]
    }
  }
}

The command is identical everywhere — only the file it goes in differs. Start one shared hub separately with npx -y @wcgw/vibe-check-mcp@0.3.0 hub before launching the client.

Claude Desktop

Add the block to Claude Desktop's config file, then fully quit and reopen the app (a window reload is not enough):

OSConfig file
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json

If the file doesn't exist yet, create it with just the mcpServers object above. After restarting, the tools appear under the MCP/tools menu in the composer.

Windsurf and others

Most other clients (Windsurf, Cline, Zed, and so on) read a mcpServers object too — consult your client's MCP docs for the exact file path and drop the same block in. The command / args never change.

Verify

curl http://localhost:4200/api/health   # → {"status":"ok"}

Troubleshooting

If the bridge won't load, confirm the hub is running and double-check the JSON is valid. Remember to fully restart the client after editing its config. If it loads but lists no projects, confirm the widget has the matching beaconUrl and a stable projectId. See Troubleshooting.