Integrations
Cursor, Claude Code, Codex, Copilot: enabling the MCP
One command installs the MCP server. Each IDE registers it differently. Here's the exact wiring per tool.
VibeReview's MCP server runs locally and exposes the active guardrails to your coding agent. Installation is one CLI command. Wiring it into the IDE takes another minute per tool.
Install the MCP server
Run npx @vibereview/mcp install. The CLI authenticates against your VibeReview workspace, downloads the local binary, and writes the config stub each IDE needs.
Per-IDE wiring
- Cursor: open Settings → Features → MCP, paste the config stub, restart. The vibereview server appears in the MCP panel.
- Claude Code: edit ~/.claude/mcp.json and add the vibereview entry. Restart the CLI.
- Codex: configure the MCP via the OpenAI extension's settings panel. Same config stub.
- Copilot (Workspace): MCP support arrives via the agent extensibility config. The CLI emits the right file path for your version.
Verifying the connection
Open a file with a known sensitive path. Start a prompt. The MCP server logs the guardrail load. Your IDE's MCP panel shows vibereview as connected. The agent's first response should cite the rules it picked up.