Integration

MCP Server

Run preflight risk checks directly from Claude Code, Cursor, or any MCP-compatible editor. One command, zero copy-paste.

Quick Start

Add Airlock to your MCP configuration. Works with stdio transport.

// claude_desktop_config.json, .cursor/mcp.json, etc.
{
  "mcpServers": {
    "airlock": {
      "command": "airlock",
      "args": ["--mcp"],
      "env": {
        "ANTHROPIC_API_KEY": "your-api-key"
      }
    }
  }
}
        

Available Tools

Once connected, your editor gains tools for risk analysis and authorization.

preflight_change

Pre-flight risk check for proposed code changes. Call before editing files or proposing diffs. Returns a risk score (0-100), protected zone violations, blast radius, and required actions. Returns gated=true when human approval is needed.

get_context_pack

Versioned, evidence-graded context with citations and immutable receipt. Structured repository intelligence for humans and AI agents.

analyze_risk_zones

Identify high-churn, multi-author files that are risky to modify. Reasons about architectural coupling, missing tests, security-sensitive code, and active hotspots.

Works With

Airlock's MCP server follows the open Model Context Protocol standard. It works with any client that supports MCP.

Claude Code

Add to claude_desktop_config.json. Airlock runs preflight checks before every code change automatically.

Cursor / Windsurf

Add to .cursor/mcp.json or equivalent. Airlock tools appear alongside your editor's built-in AI features.

Any MCP Client

VS Code, Copilot, Gemini CLI, Goose, Roo Code, Amp, and 20+ other tools that support the MCP standard.

Usage Examples

# In Claude Code, Airlock runs automatically before changes:
"Run a preflight check on this PR before merging"

# Analyze risk zones in a repo:
"Use airlock to find risk zones in this repo"

# Check specific files before editing:
"Preflight check: I want to modify src/auth/session.rs"
        