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

# Integrations

> Connect Ona to source control, work trackers, docs, incident tools, and cloud providers.

Ona integrations fall into three categories:

* **Source control** for cloning repositories, pushing commits, and letting agents interact with pull requests and issues
* **Tool integrations** for giving agents access to work trackers, docs, incident tools, and other MCP-backed services
* **Cloud access** for federating from environments into providers like AWS without long-lived credentials

This page is the overview. Use the linked setup guides for provider-specific steps.

## Source control

Source control is the foundational integration in Ona. It gives environments access to your repositories and lets agents work with the same permissions your developers already have.

* [Source control overview](/ona/source-control/overview)
* [GitHub & GitLab agent tools](/ona/agents/scm-tools)

Supported providers:

| Provider                                         | Repo access | Agent API tools |
| ------------------------------------------------ | ----------- | --------------- |
| [GitHub](/ona/source-control/github)             | Yes         | Yes             |
| [GitLab](/ona/source-control/gitlab)             | Yes         | Yes             |
| [Bitbucket Cloud](/ona/source-control/bitbucket) | Yes         | No              |
| [Azure DevOps](/ona/source-control/azuredevops)  | Yes         | No              |

## Tool integrations for agents

Most non-SCM integrations are exposed to agents through the [Model Context Protocol (MCP)](/ona/mcp). There are two distinct layers, and both must be in place before an agent can use a tool:

* **Organization integrations** are configured by an administrator in your organization settings. They turn an integration on for the org (e.g., "Linear is allowed in this organization") and provide the OAuth client and any shared configuration. Without this, the integration does not appear to users.
* **Per-user MCP authentication** happens after the org integration is enabled. Each user authenticates the integration with their own account so the agent acts with their permissions, not a shared service account.

In short:

1. **Organization-level enablement** by an administrator
2. **User authentication** so the agent acts with your permissions

<img src="https://mintcdn.com/gitpod-13c83c2b/00KFAvcXHAexvnrd/images/agents/linear-org-integration-settings.png?fit=max&auto=format&n=00KFAvcXHAexvnrd&q=85&s=55586e7583150a47d1a9ee600bc42e22" alt="Organization integration settings" width="2152" height="1504" data-path="images/agents/linear-org-integration-settings.png" />

<img src="https://mintcdn.com/gitpod-13c83c2b/khTq7IXAxsqSVSV1/images/agents/linear-user-integration-auth.png?fit=max&auto=format&n=khTq7IXAxsqSVSV1&q=85&s=d5c7e4273e3f682f103a20c0f9ea5229" alt="User authentication for an integration" width="2272" height="1624" data-path="images/agents/linear-user-integration-auth.png" />

Available integrations:

| Integration | What agents can do                                                 | Setup                                                        |
| ----------- | ------------------------------------------------------------------ | ------------------------------------------------------------ |
| Linear      | Read issues, update status, use backlog context                    | [Configure Linear](/ona/integrations/configure-linear)       |
| Atlassian   | Work with Jira and Confluence                                      | [Configure Atlassian](/ona/integrations/configure-atlassian) |
| Notion      | Search and read workspace docs                                     | [Configure Notion](/ona/integrations/configure-notion)       |
| Sentry      | Inspect errors and issue context                                   | [Configure Sentry](/ona/integrations/configure-sentry)       |
| Granola     | Search meeting notes and transcripts                               | [Configure Granola](/ona/integrations/configure-granola)     |
| GitHub App  | Mention `@ona-agent` on a pull request to start an agent on the PR | [GitHub App](/ona/integrations/configure-github)             |

To check status during a session, open the **MCP Integrations** panel in the prompt input.

<img src="https://mintcdn.com/gitpod-13c83c2b/00KFAvcXHAexvnrd/images/agents/chat-integrations.png?fit=max&auto=format&n=00KFAvcXHAexvnrd&q=85&s=5bc7083746584fc2b836c96e424ca889" alt="MCP Integrations panel in the session input" width="1146" height="1720" data-path="images/agents/chat-integrations.png" />

## Cloud access

Ona environments can also federate into cloud providers using short-lived credentials instead of static secrets.

* [OpenID Connect (OIDC)](/ona/configuration/oidc) for the core model
* [AWS access from Ona](/ona/integrations/aws) for the AWS-specific setup

GCP follows the same OIDC pattern described in the OIDC guide.

## Related tools

Some things that used to get lumped in as "integrations" are better understood as developer interfaces or launch methods:

* [CLI](/ona/integrations/cli)
* [Ona SDK](/ona/integrations/sdk)
* [Personal access tokens](/ona/integrations/personal-access-token)
* [Browser extension](/ona/integrations/browser-extension)
* [Open from URL](/ona/integrations/ona-url)
* [README button](/ona/integrations/readme-button)
* [Port sharing](/ona/integrations/ports)