Integrations overview

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 do not go straight to an agent. Each one goes through Qualification first, which stops duplicates, already-fixed issues and requests it cannot verify, and turns the rest into tasks or plans. An issue tracker is a wish list, and not everything on it should be built.

Work also comes in without anyone importing it:

• GitHub App events. An event automation can send a pull request, a new issue or a comment that mentions Coroid to Qualification. See Triggers and destinations. Checking and reviewing every pull request is set in Quality Control, under Pull requests.
• Slack, Telegram and Jira. An event automation can send a Slack or Telegram message that matches its filter to Qualification. Of the chat platforms, only Slack and Telegram can file requests. New Jira issues need Coroid's Jira webhook, which is not set up on coroid.ai yet. See Starting work from a channel.
• The work intake API. A service account files requests from your own systems. See From your own systems.
• Coroid's MCP server. An assistant or agent such as Hermes, Codex or Claude Code works with your projects and work through Coroid's tools. See Coroid as an MCP server.

Notifications going out#

In-app notifications need no integration. Email carries account messages, not work updates.

Slack is the only chat platform that receives updates: task updates, through a Slack incoming webhook. Slack and Telegram messages can also become requests, through an event automation. Discord and SMS do neither. See Chat platforms.

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#

What to connect first#

1. Source control. Nothing works without it.
2. Slack, if your team works there. Requests then come from where people already talk.
3. Your existing evidence providers. Immediate value, no new tooling.

Everything else can wait until you have a reason.

Related#

• Hooks
• Review evidence