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

# Oplane Documentation

> Official Oplane documentation for connecting GitHub or GitLab repositories, configuring automated threat modeling, and securing your dev workflow.

AI-powered threat modeling that finds architectural security risks in your pull requests — before they reach production.

<CardGroup cols={2}>
  <Card title="Get started" icon="rocket" href="/introduction">
    Connect Oplane to your repositories and run your first threat model.
  </Card>

  <Card title="MCP integration" icon="terminal" href="/mcp-agent">
    Run threat models directly from Cursor or Claude Code while you write code.
  </Card>

  <Card title="GitHub integration" icon="github" href="/connect-github">
    Automatically review pull requests for architectural security risks.
  </Card>

  <Card title="GitLab integration" icon="gitlab" href="/gitlab-setup">
    Sign in with GitLab to enable threat modeling on merge requests.
  </Card>
</CardGroup>

***

## Common tasks

<CardGroup cols={2}>
  <Card title="Connect GitHub" icon="git-pull-request" href="/connect-github">
    Install the Oplane GitHub App and enable automated PR reviews via a managed workspace.
  </Card>

  <Card title="Connect GitLab" icon="gitlab" href="/gitlab-setup">
    Sign in with GitLab to enable threat modeling on merge requests.
  </Card>

  <Card title="Set up MCP" icon="cpu" href="/mcp-agent">
    Connect Oplane to Cursor or Claude Code for in-IDE threat modeling.
  </Card>

  <Card title="Pull & Merge Requests" icon="shield-check" href="/github-prs">
    Learn how Oplane reviews your PRs and MRs with inline security comments.
  </Card>

  <Card title="Workspaces" icon="folder" href="/workspaces">
    Organise threat models by project, team, or repository.
  </Card>

  <Card title="How Oplane compares" icon="scale" href="/security-comparison">
    See how Oplane's threat modeling approach differs from code-scanning tools.
  </Card>
</CardGroup>