Skip to main content
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. Supported providers:

​
Tool integrations for agents

Most non-SCM integrations are exposed to agents through the Model Context Protocol (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.
  • Principal authentication happens after the org integration is enabled. Users connect personal accounts from User Settings > Integrations. Service accounts connect from the service account details page so automations can run with service-account credentials.
In short:
  1. Organization-level enablement by an administrator
  2. User or service-account authentication so the agent acts with the right identity
Organization integration settings User authentication for an integration Available integrations: To check status during a session, open the MCP Integrations panel in the prompt input. MCP Integrations panel in the session input

​
Cloud access

Ona environments can also federate into cloud providers using short-lived credentials instead of static secrets. GCP follows the same OIDC pattern described in the OIDC guide. Some things that used to get lumped in as “integrations” are better understood as developer interfaces or launch methods: