- Git Integrations: provide Overcut read and write access to your source code so agents can review, generate, and commit changes directly in your repositories.
- Ticket Integrations: allow Overcut to read, create, and update issues so agents can respond to bugs, feature requests, or tasks in the systems where you plan work.
- Chat Integrations: bring Overcut into team conversations so you can trigger workflows from the channels where work happens.
Choose the right connection path
Use workspace integrations first when Overcut already supports your provider directly. For most teams, this is the best starting point for GitHub, GitLab, Azure DevOps, Jira, Linear, ClickUp, and Slack because setup happens inside your workspace and built-in tools work automatically once the connection is in place. Use MCP servers when you want to connect a third-party system that does not have a native Overcut integration. You can also use MCP as a supplemental or fallback option for first-class providers when you need external tools or capabilities that are outside the native integration path.- See MCP Servers for setup and configuration details.
- Browse the MCP Catalog to install common third-party servers faster.
More integrations are on the roadmap. Let us know which systems you’d like to see next.
Git Integrations
Use native workspace integrations for supported Git providers so agents can work with your repositories through Overcut’s built-in tools. Overcut can connect to the following Git providers:- GitHub - Connect to GitHub repositories and issues
- GitLab - Connect to GitLab.com or self-hosted GitLab repositories and issues.
- Azure DevOps - Connect to Azure DevOps repositories and work items
- Bitbucket - Connect to Bitbucket Cloud repositories and pull requests from Overcut Cloud or a self-hosted Overcut deployment
Learn more about our security architecture, data handling, and privacy practices in our Privacy and Security documentation.
Repository Configuration
Each connected repository now exposes a Configuration panel where workspace admins can override agent behaviour for that specific codebase.| # | Setting | Default | Purpose |
|---|---|---|---|
| ① | Agent image | (workspace default) | Choose the container environment agents run in. See Agent Image. |
| ② | Enable cache | false | Persist build artefacts to speed up subsequent runs. |
| ③ | Cache dependencies | false | Include dependency directories (e.g., node_modules). |
| ④ | Tools | [] | Define repo-specific commands like lint, test, install. |
| ⑤ | Custom instructions | null | Inject additional workflow steps (YAML/Markdown). |
Ticket Integrations
Use native workspace integrations for supported ticketing systems so agents can read and update work where your team already plans and tracks delivery. To keep your planning and tracking in sync, Overcut also integrates with popular issue-tracking systems:- GitHub Issues - Integrated with GitHub repositories
- Jira - Connect to Jira Cloud workspaces from Overcut Cloud or a self-hosted Overcut deployment
- GitLab Issues - Integrated with GitLab repositories
- Azure DevOps Work Items - Integrated with Azure DevOps repositories
- Linear - Connect to Linear workspaces and teams
- ClickUp - Connect to ClickUp workspaces and Spaces for task operations
Ticket links depend on your provider
Some ticket integrations also let agents work with linked relationships between tickets. When a provider supports ticket links, agents can create links, remove links, and read existing relationships to understand how related work connects across your backlog. Available relationship types are defined by the connected provider rather than by one shared Overcut list. Before creating a link, agents can inspect the relationship types that provider makes available and choose from the supported options. Cross-project linking also depends on the connected provider. Some providers allow links across projects or teams, while others limit links to work that lives in the same project, workspace, or repository.What agents can do with linked tickets
When ticket links are supported by your provider, agents can:- Create linked relationships between tickets
- Remove linked relationships that are no longer needed
- Read existing links and use them as context when reasoning about related work
- Inspect the relationship types your provider supports before creating a link
For agents to work with ticket links, make sure the relevant ticket tools (
link_tickets, unlink_tickets, and get_ticket_metadata) are selected for the agent in Agent Roles → agent settings. See the tools reference for the full list.Chat Integrations
Use native workspace integrations for supported chat providers so teams can trigger workflows directly from their existing conversations. Chat integrations let your team start workflows from the conversations where work already happens.- Slack: connect Slack at the workspace level, register channels inside each project, and trigger workflows from registered channels.
Custom Events (generic webhooks)
For any third-party system Overcut does not have a native integration for, Custom Events let a workspace admin define an event type, get a public webhook URL, and pick an authentication mode. Any tool that can send an HTTP request (CI servers like Jenkins, monitoring tools like Datadog or Grafana, internal scripts, low-code platforms) can then fire workflows in the projects you authorize.- Custom Events: setup, authentication, project scoping, and ready-to-paste recipes for curl, Jenkins, Datadog, and Grafana.