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

# Integrations Overview

> Compare core integrations and MCP server integrations in OpenHands Enterprise, and see what each integration supports.

OpenHands Enterprise supports two types of integrations: **core integrations** and **MCP server integrations**.

* **Core integrations** are built-in connections to Git, ticketing, and chat providers. An admin configures them for
  the whole instance, and events in those systems, such as an `@openhands` mention, can start OpenHands workflows.
* **MCP server integrations** give the agent access to external tools and data during a conversation. Each user
  connects their own MCP servers, and the agent calls them only when it needs them.

| Dimension | Core integrations | MCP server integrations |
| - | - | - |
| Purpose | Purpose-built integrations for OpenHands Enterprise | Extend agent access to external systems through MCP servers |
| Data flow | Bidirectional (outbound and event-driven) | Unidirectional (outbound only) |
| Integrations | Git and ticketing providers: GitHub, GitLab, Bitbucket Cloud, Bitbucket Data Center, Azure DevOps, Jira Cloud, Jira Data Center, Slack | Large MCP catalog across multiple integration categories |
| Authentication | OAuth | OAuth or bearer token |
| Administration | Super admins enable or disable specific integrations and configure their OAuth app IDs, client IDs, and client secrets | End users manage their own MCP connections |
| Navigation | `Settings > Integrations` | `Customize > MCP Servers` |
| When to use | The recommended way to integrate with supported Git and ticketing providers | When you need to call a third-party service from within an agent conversation |

## Core Integrations

Core integrations are purpose-built for OpenHands Enterprise. A super admin configures them at the instance level and
chooses which integrations are available in the product.

Core integrations support these use cases:

* Fetching repositories and cloning them in conversations.
* Running resolver workflows by mentioning OpenHands in an issue or pull request, or by applying an OpenHands label.
* Signing in to OpenHands Enterprise as an alternative authentication mechanism.

### Git Providers

Git integrations let users:

* Fetch repositories and start conversations about them in sandboxes.
* Run resolver workflows by mentioning OpenHands in an issue or pull request, or by applying an OpenHands label.

Some Git providers also include ticketing capabilities, including GitHub, Azure DevOps, and GitLab.

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/enterprise/integrations/github">
    Configure the GitHub App and the built-in GitHub resolver.
  </Card>

  <Card title="GitLab" icon="gitlab" href="/enterprise/integrations/gitlab">
    Connect GitLab SaaS or self-managed GitLab and install repository webhooks.
  </Card>

  <Card title="Bitbucket Cloud" icon="bitbucket" href="/openhands/usage/cloud/bitbucket-installation">
    Fetch and clone Bitbucket Cloud repositories.
  </Card>

  <Card title="Bitbucket Data Center" icon="bitbucket" href="/enterprise/integrations/bitbucket-data-center">
    Configure Bitbucket Data Center sign-in and repository webhooks.
  </Card>

  <Card title="Azure DevOps" icon="microsoft" href="/enterprise/integrations/azure-devops">
    Connect Azure Repos and Azure Boards with Microsoft Entra ID sign-in.
  </Card>
</CardGroup>

### Ticketing Platforms

Ticketing integrations support resolver workflows directly in tickets. Users can mention OpenHands or add an OpenHands
label to start a conversation from the ticket.

<CardGroup cols={2}>
  <Card title="Jira Cloud" icon="jira" href="/enterprise/integrations/jira-cloud">
    Start OpenHands from Jira Cloud issues with a mention or label.
  </Card>

  <Card title="Jira Data Center" icon="jira" href="/enterprise/integrations/jira-data-center">
    Start OpenHands from Jira Data Center issues with a mention or label.
  </Card>
</CardGroup>

### Slack / ChatOps

An administrator can enable or disable Slack. Setup requires creating a Slack app and providing its connection details.
Once configured, users can mention OpenHands in a Slack thread or channel to start a conversation directly in Slack.

<CardGroup cols={2}>
  <Card title="Slack" icon="slack" href="/enterprise/integrations/slack">
    Start and follow up on conversations by mentioning `@openhands` in Slack.
  </Card>
</CardGroup>

### Use as an Authentication Identity Provider

Some core integrations can also serve as sign-in options for OpenHands Enterprise, including GitHub, Azure DevOps,
Bitbucket Data Center, and GitLab. We still recommend configuring SAML SSO with your own identity provider.

<CardGroup cols={2}>
  <Card title="SAML SSO" icon="user-shield" href="/enterprise/integrations/saml-sso">
    Let users sign in with Okta, Microsoft Entra ID, Google Workspace, ADFS, or Authentik.
  </Card>
</CardGroup>

### Bidirectional and Event-Driven

Core integrations are **bidirectional** and **event-driven**. In addition to OpenHands interacting with the
integration, events in the external system can trigger OpenHands workflows.

### Integration Coverage

* **Fetch repos**: Fetch and clone repositories (Git providers only).
* **Resolver**: Use OpenHands in conversations, issues, and pull requests.
* **Auth IdP**: Sign in to OpenHands Enterprise through the integration.

| Integration | Fetch repos | Resolver | Auth IdP |
| - | - | - | - |
| [GitHub](/enterprise/integrations/github) | ✅ | ✅ | ✅ GitHub App sign-in |
| [GitLab](/enterprise/integrations/gitlab) (SaaS and self-managed) | ✅ | ✅ | ✅ |
| [Bitbucket Data Center](/enterprise/integrations/bitbucket-data-center) | ✅ | ✅ | ✅ |
| [Bitbucket Cloud](/openhands/usage/cloud/bitbucket-installation) | ✅ | ❌ | ❌ |
| [Azure DevOps](/enterprise/integrations/azure-devops) | ✅ Azure Repos | Supported, but requires an [event-based automation](/enterprise/integrations/azure-devops#trigger-openhands-from-azure-devops) | ✅ Microsoft Entra ID |
| [Jira Cloud](/enterprise/integrations/jira-cloud) | N/A | ✅ | ❌ |
| [Jira Data Center](/enterprise/integrations/jira-data-center) | N/A | ✅ | ❌ |
| [Slack](/enterprise/integrations/slack) | N/A | ✅ | N/A |
| [SAML SSO](/enterprise/integrations/saml-sso) (Okta, Entra ID, Google Workspace, ADFS, Authentik) | N/A | N/A | ✅ Recommended sign-in method |

## MCP Server Integrations

MCP server integrations provide additional ways for users to connect external systems to OpenHands. They support
multiple server types, including SSE, streamable HTTP (SHTTP), and stdio, as well as authentication methods such as
bearer tokens and OAuth.

Examples include:

* **OAuth-enabled**: Atlassian Rovo, GitLab, Granola
* **Token-enabled**: Linear, Notion

Unlike core integrations, MCP servers are **unidirectional**: the OpenHands agent calls the MCP server to access data,
rather than receiving external events from it.

See [MCP Settings](/openhands/usage/settings/mcp-settings) to add and configure MCP servers.

## Agentic Infrastructure

<CardGroup cols={2}>
  <Card title="External LLM Gateways" icon="network-wired" href="/enterprise/integrations/external-llm-gateways">
    Route LLM traffic through your existing LiteLLM or Bifrost gateway for routing, cost tracking, and audit.
  </Card>

  <Card title="External Observability Platforms" icon="chart-line" href="/enterprise/integrations/observability-platforms">
    Send conversation traces to your own OTLP-compatible platform, such as Langfuse, Honeycomb, or Tempo.
  </Card>
</CardGroup>