Coroid sits between the tools you already use. This page outlines what connects where and in which direction — the direction is usually the first thing people need to determine.
Source control — required
The only integration Coroid cannot function without.
GitHub — app install or personal access token. Generally available.
GitLab — personal access token. In private preview, visible only on accounts where it has been enabled.
Coroid reads your repository and opens pull requests against it. See Connect your code.
Incoming work
Issue trackers feed work into Coroid: Jira, Linear, Trello and GitHub Issues.
Imported issues land in the intake queue rather than being processed straight away; you route each one manually — an issue tracker is a wish list, and not everything on it should be built by an agent without human input.
Outgoing notifications
Chat platforms receive updates: Slack, Discord, Telegram, and SMS. Email and in-app notifications work without any integration.
Some chat connections are bidirectional, allowing people to start and steer work from the channel they already use.
Returned evidence
Around thirty providers can attach verification evidence to pull requests — preview deployments, security and code scanners, coverage reports, visual diffs, and end-to-end tests.
This is usually the most valuable integration after source control, as most teams already use these tools but do not see their output alongside the changes. See Review evidence.
MCP — bidirectional
Two distinct things that are easily confused:
Outbound — Coroid connects to your MCP servers. Agents call tools you provide, enabling work to reach internal systems that Coroid knows nothing about.
Inbound — Coroid acts as an MCP server. Your own tools and assistants drive Coroid via a remote MCP endpoint using OAuth or a personal access token, with an approval queue and automation policies controlling what can happen automatically.
Events and automation
Hooks They respond to platform events with instructions you write and can call external tools.
Audit events can be exported to your SIEM, and enterprise identity links SSO/SAML via SCIM provisioning.
Where to configure
| Integration | Where |
|---|---|
| Source control | Settings → Connections → Source control |
| Chat platforms | Settings → Connections → Channels |
| External MCP servers | Settings → Connections → External MCP |
| Coroid's MCP server | Settings → Automation → Coroid MCP server |
| Hooks and webhooks | Settings → Automation → Automations |
| Review evidence | Project settings → Integrations |
What to connect first
- Source control. Nothing works without it.
- One chat channel. Notifications that people actually see.
- Your existing evidence providers. Immediate value, no extra tooling required.
Everything else can wait until you have a specific reason to use it.