Quickstart

Get up and running with Corridor in a few quick steps. This assumes you have a Corridor account (sign up at app.corridor.dev) and access to the code repository you want to secure.

Prerequisites

A Corridor account (sign up)
A supported IDE or AI coding tool (VS Code, Cursor, Claude Code, Devin Desktop, Factory, Devin, Codex, or any MCP-compatible tool)
A GitHub repository to connect

Step 1: Connect GitHub

In the Corridor web app, you’ll be prompted to connect your GitHub account or organization. Authorize the Corridor GitHub App with the necessary permissions.

Go to app.corridor.dev and sign in with your GitHub account.

Authorize GitHub

Click Connect GitHub and authorize the Corridor GitHub App. You can grant access to All repositories or select specific repos—be sure to include any repos you want Corridor to monitor.

Corridor needs read access to code and permission to write PR comments to perform reviews.

Step 2: Add a project (repository)

Once GitHub is connected, add a repository as a Project in Corridor.

Go to Projects

In the Corridor dashboard, go to Projects and click New Project.

Select repository

Select the repo from the list to bring it under Corridor’s protection. You must add a project before Corridor can analyze its code—simply connecting GitHub isn’t enough.

Auto-generated guardrails

After adding, Corridor will scan the codebase and automatically generate initial security guardrails tailored to that project.

Step 3: Install the IDE extension

To get real-time guardrails while coding, install Corridor’s integration for your development environment:

Open VS Code
Go to the Extensions panel (Cmd+Shift+X or Ctrl+Shift+X)
Search for “Corridor”
Click Install
Reload your editor when prompted

After installation, you’ll see the Corridor icon in your sidebar.

GitHub Copilot users: If your organization manages Copilot through GitHub Enterprise, an admin must enable external MCP servers in the Copilot policy settings before Corridor’s tools will appear.

See VS Code setup for detailed instructions.

Cursor has two Corridor integrations. You can use either or both at the same time.Option 1: Cursor Plugin — available in the Cursor Marketplace. Includes the /corridor skill to review code in the background as Cursor Agents work. Use this for a frictionless, Cursor-native experience with the least setup.

In Cursor, open the Agents tab and navigate to the Marketplace
Find Corridor and click Get
Click New Agent and configure it as Local
Invoke the skill in any chat with /corridor

Option 2: Corridor extension — a VS Code-style extension that registers Corridor as an MCP server and runs deterministic hooks. Use this for access to all Corridor features, such as MCP-based tool access, MCP compliance enforcement, or hooks that can block code with critical findings.

Open the Extensions panel in Cursor (Cmd+Shift+X or Ctrl+Shift+X)
Search for “Corridor” and click Install
Reload Cursor and sign in from the Corridor sidebar

See Cursor setup for detailed instructions on both options.

Integrate Corridor with Claude Code via the CLI.

Install the Corridor CLI:

# macOS / Linux
curl -fsSL https://app.corridor.dev/cli/install.sh | bash

# Windows (PowerShell)
irm https://app.corridor.dev/cli/install.ps1 | iex

The installer will automatically set up the Corridor plugin, MCP server, and hooks

See Claude Code setup for detailed instructions.

Integrate Corridor with Factory’s AI Droid agents via MCP and hooks.

Install the Corridor CLI:

# macOS / Linux
curl -fsSL https://app.corridor.dev/cli/install.sh | bash

# Windows (PowerShell)
irm https://app.corridor.dev/cli/install.ps1 | iex

The installer will automatically set up the Corridor plugin, MCP server, hooks, and agent rules

See Factory setup for detailed instructions.

Integrate Corridor with the Codex CLI via MCP and hooks.

Install the Corridor CLI:

# macOS / Linux
curl -fsSL https://app.corridor.dev/cli/install.sh | bash

# Windows (PowerShell)
irm https://app.corridor.dev/cli/install.ps1 | iex

The installer detects the codex binary and automatically sets up the Corridor plugin, MCP server, hooks (macOS), and agent rules

See Codex setup for detailed instructions.

Integrate Corridor with Devin via MCP.

Generate a Corridor API token at app.corridor.dev/settings
In Devin, go to Organization settings → MCP Marketplace and add Corridor
In the CORRIDOR_AUTHORIZATION secret, enter Bearer followed by a space and your token, for example Bearer cor_your_token_here
Add new knowledge pinned to all repositories with a prompt instructing Devin to always call Corridor when generating code

See Devin setup for detailed instructions.

Open the Extensions panel in Devin Desktop (Cmd+Shift+X or Ctrl+Shift+X)
Search for “Corridor” and click Install
Reload your editor when prompted
Click the Corridor icon in the sidebar and sign in to your Corridor account

See Devin Desktop setup for detailed instructions.

Integrate Corridor with any MCP-compatible tool.

Generate a Corridor API token in your Corridor settings

Configure your MCP client with the following:

{
  "mcpServers": {
    "corridor": {
      "transport": "http",
      "url": "https://app.corridor.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer {generated_token}"
      }
    }
  }
}

Replace {generated_token} with your Corridor API token.

See Custom MCP setup for detailed instructions.

Step 4: (Optional) Invite team members

If you’re on a Team or Enterprise plan, you can invite colleagues to join your Corridor workspace so they can benefit from the same guardrails and visibility.

Open the Teams page

In the Corridor web app, go to the Teams page.

Invite members

Click Invite Member, enter their email, select a role, and click Send Invite.

See Inviting Teammates for details. Skip this if you’re an individual user.

You’re all set

That’s it—Corridor is now set up! From this point on:

In the IDE: Your AI assistant (e.g. Cursor or Claude Code) will consult Corridor’s guardrails as you generate code, stopping insecure suggestions
For Pull Requests: Corridor will automatically review new PRs on your connected project. You’ll see comments or checks on the PR if any vulnerabilities are found
Dashboard: You can monitor findings and adjust settings via the Corridor Dashboard

You’ve successfully onboarded Corridor to your project—secure coding can now happen in real-time without breaking your flow.

Getting Started

Onboarding

IDE Setup

Long-Running Agents

Features

Agent Governance

Integrations

Administration

Prerequisites

Step 1: Connect GitHub

Step 2: Add a project (repository)

Step 3: Install the IDE extension

Step 4: (Optional) Invite team members

You’re all set

Next steps

Guardrails

PR Reviews

​Prerequisites

​Step 1: Connect GitHub

​Step 2: Add a project (repository)

​Step 3: Install the IDE extension

​Step 4: (Optional) Invite team members

​You’re all set

​Next steps

Guardrails

PR Reviews

Prerequisites

Step 1: Connect GitHub

Step 2: Add a project (repository)

Step 3: Install the IDE extension

Step 4: (Optional) Invite team members

You’re all set

Next steps