Skip to main content
Corridor integrates with Claude Code via MCP and hooks, ensuring that code generated by Claude Code is checked against your security guardrails.

Prerequisites

  • Claude Code installed (claude command)
  • A Corridor account with a team created

Setup

1

Install the Corridor CLI

Install the Corridor CLI with a single command:
curl -fsSL https://app.corridor.dev/cli/install.sh | bash
The CLI auto-updates on startup, so you’ll always have the latest version.The installer will run corridor install automatically to set up the Corridor plugin, MCP server, and hooks.
2

Update CLAUDE.md

Update your CLAUDE.md to include Corridor’s prompt so Claude Code always calls Corridor when generating code. Add the following to your CLAUDE.md:
# Corridor Security Analysis
Every time you generate code, use the analyzePlan tool from Corridor's MCP Server (corridor) to analyze the plan or thought process. ALWAYS use Corridor to analyze the plan. Always generate a plan before generating code.
This ensures Claude Code consults Corridor’s guardrails on every task.
3

Verify the plugin

Restart Claude Code if it’s currently running. You can verify the plugin is connected by running /mcp in Claude Code.
Once configured, Claude Code will invoke Corridor’s security checks as it writes code, catching vulnerabilities and enforcing your security policies automatically.

Hooks

Hooks are deterministic scripts that run at specific points in the code generation process, enabling real-time security reviews and policy enforcement. Hooks are automatically set up by the Corridor CLI.

MCP compliance

Corridor tracks which MCP servers are active and enforces your team’s policies. To configure, navigate to the Compliance tab in the Corridor dashboard and choose Allowlist Mode or Blocklist Mode.

Uninstalling

To remove the Corridor plugin and all its configuration, run:
corridor uninstall
You’ll be prompted for confirmation before anything is removed. To skip the prompt (for example, in CI), use --non-interactive:
corridor uninstall --non-interactive

Next steps