Corunner Integrations: Direct Connections and MCP Servers

Corunner integrations come in two shapes: Direct Connections native to the product and MCP Servers that speak the Model Context Protocol.

Corunner integrations come in two shapes. Direct Connections are native to Corunner and expose dedicated capabilities such as reading issues, posting messages, or subscribing to webhook events. MCP Servers are Model Context Protocol servers that Corunner registers on your behalf so agents can query them like any other tool. Both live under Integrations in the web app, on separate tabs.

Every integration inherits the permissions of the account or token you connect with. Corunner never asks for more access than the connector needs.

Direct Connections

Native connectors with dedicated capabilities. Corunner authenticates with the vendor using one of five methods:

Auth type	What it looks like
OAuth	You approve scopes in a browser popup during the connect flow.
API Key	You paste a key you generated in the vendor’s admin console.
Personal Access Token (PAT)	You paste a token you created in your vendor account.
Atlassian Forge app	Corunner ships as a Forge app that you install from the Atlassian Marketplace.
Service Account	Your admin creates a machine account in the vendor with the read scopes Corunner needs.

GitHub

Repositories, pull requests, and CI checks.

Linear

Issues, blockers, and standup enrichment.

Jira & Confluence

Issue sync, tickets, and Confluence pages.

Salesforce

Pipeline, accounts, and opportunities.

HubSpot

Deals, contacts, and pipelines.

Datadog

Monitors, incidents, and metrics.

MCP Servers

Corunner can register any Model Context Protocol server and expose its tools to agents. Use MCP for read-only knowledge, product analytics, design context, or custom internal tools that already speak MCP.

Notion

Docs, databases, and organizational memory.

Confluence

Spaces and pages via MCP.

Google Drive

Search and retrieve files.

Figma

Design files, frames, and specs.

PostHog

Product analytics through MCP.

Custom MCP Server

Register any MCP-compatible server.

Adding an integration

1. Open Integrations

   In the Corunner web app, go to Integrations.

2. Pick the connector

   Choose the Direct Connections tab for native integrations, or MCP Servers for MCP.

3. Complete the connect flow

   OAuth pops a consent window. API key, PAT, service account, and Forge flows use the fields in the connection card.

4. Verify

   A successful connection turns the card into a connected state. Agents can now use the new tool immediately.

Adding, editing, or disconnecting integrations is admin-only. See Roles & Access.

New connectors ship regularly. If you want a tool that is not listed today, register it through Custom MCP Server or ask your Corunner contact whether a native connector is on the roadmap.