Coroid sits in the middle of tools you already use. This page maps what connects where and in which direction — the direction is usually what people need to work out first.
Source control — required
The only integration Coroid cannot work 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.
Work coming in
Issue trackers feed work into Coroid: Jira, Linear, Trello and GitHub Issues.
Imported issues arrive in the intake queue rather than executing immediately, and you route each one yourself — an issue tracker is a wish list, and not everything on it should be built by an agent without a human deciding.
Notifications going out
Chat platforms receive updates: Slack, Discord, Telegram, and SMS. Email and in-app notifications work without any integration.
Some chat connections are bidirectional, letting people start and steer work from the channel they already talk in.
Evidence coming back
Around thirty providers can attach verification evidence to pull requests — preview deployments, security and code scanners, coverage, visual diffs and end-to-end runs.
This is usually the highest-value integration after source control, because most teams already have these tools and are simply not seeing their output next to the change. See Review evidence.
MCP — both directions
Two distinct things that are easy to confuse:
Outbound — Coroid connects to your MCP servers. Agents call tools you provide, so work can reach internal systems Coroid knows nothing about.
Inbound — Coroid is an MCP server. Your own tools and assistants drive Coroid over a remote MCP endpoint with OAuth or a personal access token, with an approval queue and automation policies governing what may happen unattended.
Events and automation
Hooks react to platform events with instructions you write, and can call out to external tools.
Audit events can be exported to your SIEM, and enterprise identity connects SSO/SAML with 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 people actually see.
- Your existing evidence providers. Immediate value, no new tooling.
Everything else can wait until you have a reason.