- 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
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:| Provider | Repo access | Agent API tools |
|---|---|---|
| GitHub | Yes | Yes |
| GitLab | Yes | Yes |
| Bitbucket Cloud | Yes | No |
| Azure DevOps | Yes | No |
Tool integrations for agents
Most non-SCM integrations are exposed to agents through the Model Context Protocol (MCP). They require:- Organization-level enablement by an administrator
- User authentication so the agent acts with your permissions
| Integration | What agents can do | Setup |
|---|---|---|
| Linear | Read issues, update status, use backlog context | Configure Linear |
| Atlassian | Work with Jira and Confluence | Configure Atlassian |
| Notion | Search and read workspace docs | Configure Notion |
| Sentry | Inspect errors and issue context | Configure Sentry |
| Granola | Search meeting notes and transcripts | Configure Granola |
Cloud access
Ona environments can also federate into cloud providers using short-lived credentials instead of static secrets.- OpenID Connect (OIDC) for the core model
- AWS access from Ona for the AWS-specific setup