Skip to main content
Corridor integrates with Factory’s AI Droid agents via MCP and hooks, ensuring that code generated by Factory agents is checked against your security guardrails.

Prerequisites

  • A Factory account
  • A Corridor account with a team created

Setup

1

Install the Corridor CLI

Install the Corridor CLI with a single command:macOS / Linux:
curl -fsSL https://app.corridor.dev/cli/install.sh | bash
Windows (PowerShell):
irm https://app.corridor.dev/cli/install.ps1 | iex
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

Verify the plugin

Restart Factory Droid if it’s currently running. The Corridor plugin will be automatically configured with the necessary agent rules and MCP server settings.
Once configured, the Factory Droid agent 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 Factory Droid invokes and enforces your team’s policies. To configure, navigate to the Compliance tab in the Corridor dashboard and choose Allowlist Mode or Blocklist Mode. See MCP Compliance for details.

Troubleshooting hooks

If hooks are not running:
  • Run corridor install --force to reinstall hooks
  • Verify the plugin is registered in ~/.factory/settings.json

Uninstalling

To remove the Corridor CLI and all its configuration, run the uninstall script:
curl -fsSL https://app.corridor.dev/cli/uninstall.sh | bash
The script removes the Corridor plugin, MCP server, hooks, and the corridor binary from ~/.corridor and ~/.local/bin.

Next steps

Guardrails

Learn how guardrails protect your code

Corridor MCP

Explore Corridor’s MCP tools