> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corridor.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Windsurf

> Integrate Corridor with Windsurf for real-time security guardrails via MCP and hooks.

Corridor integrates with Windsurf through the Corridor extension, providing real-time security guardrails as you code with AI assistants via MCP and hooks.

## Prerequisites

* Windsurf installed
* A Corridor account with a team created

## Installation

<Steps>
  <Step title="Open the Extensions panel">
    In Windsurf, open the Extensions panel by pressing `Cmd+Shift+X` (macOS) or `Ctrl+Shift+X` (Windows/Linux).
  </Step>

  <Step title="Search for Corridor">
    Type "Corridor" in the search box.
  </Step>

  <Step title="Install the extension">
    Click **Install** on the Corridor extension.
  </Step>

  <Step title="Reload your editor">
    Reload your editor when prompted, or restart it manually.
  </Step>
</Steps>

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

## Authentication

<Steps>
  <Step title="Open the Corridor panel">
    Click the Corridor icon in the activity bar.
  </Step>

  <Step title="Sign in">
    Click **Sign in to Corridor** and complete the browser authentication flow.
  </Step>

  <Step title="Verify connection">
    After authentication, your team name appears in the Corridor panel. Your AI assistant will now consult Corridor's guardrails as you generate code.
  </Step>
</Steps>

## Hooks

Hooks are deterministic scripts that run at specific points in the code generation process, enabling real-time security reviews and policy enforcement without interrupting your development flow. Hooks are automatically enabled in the latest version of the Corridor extension.

### MCP compliance

Corridor tracks which MCP servers are active in your workspace and enforces your team's policies. Unlike MCP relays, this approach integrates directly without adding latency or complexity.

To configure MCP compliance settings, navigate to the **Compliance** tab in the Corridor dashboard and choose **Allowlist Mode** (allow only specific MCP servers) or **Blocklist Mode** (block specific MCP servers).

### Troubleshooting hooks

If hooks are not running:

* Verify you're using the latest version of the Corridor extension
* Check that the extension is properly authenticated
* Ensure that you've enabled hooks in the extension

## Next steps

<CardGroup cols={2}>
  <Card title="Guardrails" icon="shield-check" href="/features/guardrails">
    Learn how guardrails protect your code
  </Card>

  <Card title="Corridor MCP" icon="plug" href="/features/corridor-mcp">
    Explore Corridor's MCP tools
  </Card>
</CardGroup>
