Integrations Overview

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.

​

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.

​

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.

​

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.

​

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.

​

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.

​

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 to add and configure MCP servers.

​

Agentic Infrastructure