vibecheck0.3.0
AI Agent Setup

Cursor

Add the VibeCheck MCP server to Cursor.

Cursor reads MCP servers from a JSON file. Add one for VibeCheck and Cursor's agent gets all nine tools. Start the shared hub separately with npx -y @wcgw/vibe-check-mcp@0.3.0 hub.

Project config

Create .cursor/mcp.json at the root of your project:

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

Commit this file to share the setup with your team. For a machine-wide server that works in every project, put the same mcpServers block in ~/.cursor/mcp.json instead.

Enable and verify

  1. Restart Cursor (or reload the window) so it picks up the new config.

  2. Open Settings → MCPvibe-check should show a green/connected status and list its tools.

  3. Confirm the HTTP receiver is up:

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

Then ask Cursor's agent:

What performance issues is VibeCheck detecting right now?

Troubleshooting

If vibe-check shows an error in Settings → MCP, check the JSON for a trailing comma or missing bracket. Confirm the hub is running before Cursor starts the connect bridge. If it connects but lists no projects, make sure the widget has beaconUrl="http://127.0.0.1:4200" and a stable projectId. See Troubleshooting.