Ctrlk
Log in|Playground
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Connectors

Connectors let individual users link their external tool accounts to groundcover, enabling Agent Mode to take actions on their behalf

Connectors link groundcover to external tools such as GitHub, Notion, PagerDuty, Claude Managed Agents, Linear, Slack, and Cursor. Depending on the connector, they can power organization-wide notification workflows, personal Agent Mode tools, or both.

Notion, Pylon, GitHub, PagerDuty, Rootly, incident.io, and Atlassian Rovo use their providers' MCP services behind first-class connector cards. Select the card directly; you do not need to configure an MCP server URL. Claude Managed Agents connects directly to Anthropic instead of using MCP.

The PagerDuty, Rootly, and incident.io connector cards give Agent Mode access to those services. To send monitor notifications, configure a PagerDuty, Rootly, or incident.io Destination instead.

Connectors vs Destinations

groundcover has two types of external integrations that serve different purposes:

Aspect
Connectors
Destinations

Scope

Personal connections, sometimes backed by an organization-managed app

Organization, admins configure shared integrations

Purpose

Enable Agent Mode to take actions in external tools on behalf of the user

Send notifications and alerts to external services

Authentication

User authorizes their account with OAuth or provides personal credentials

Admin configures org-wide credentials or authorizes a shared app

Used by

groundcover Agent Mode during conversations

Notification Routes, Monitors, and Workflows

Setup location

Integrations → Connectors

Integrations → Destinations

In short: Destinations push alerts out of groundcover at the org level, while Connectors let Agent Mode reach into external tools at the user level.

Some integrations support both roles. Setting up Linear or Slack under Org Connectors creates the organization-level connection used by monitor workflows, while My Connections lets each user authorize the same tool for Agent Mode.

How It Works

Connectors use a two-tier model:

  1. Organization setup: A workspace admin enables or configures a connector for the organization. Depending on the connector, the admin may authorize with OAuth, supply an API token, or register an OAuth application and enter its Client ID and Client Secret.

  2. User connection: Individual users authorize their account with OAuth or provide a personal token. Agent Mode uses the connection to act on the user's behalf.

Admin permissions are required to enable or disable a connector for the organization. Any workspace member with Agent Mode access can connect their own account once the connector is enabled.

Connector list in groundcover
Connectors are available as first-class cards under Integrations → Connectors.

Multiple Instances per Connector

Every connector supports multiple instances, so you can connect the same connector type to more than one external account or environment. Each instance is identified by a unique Connector Name that you choose at setup time.

Common use cases:

  • Slack — connect more than one Slack workspace by adding a separate Slack App per workspace (e.g., groundcover Prod, groundcover Staging). When selecting Slack channels, each Slack App appears separately in the destination picker so you can route alerts to the right workspace.

  • Linear — connect multiple Linear workspaces by creating a separate OAuth application and organization connector for each workspace. Each connector appears separately when creating issues or configuring Notification Routes.

  • Cursor — connect multiple Cursor API keys (e.g., one per repository owner or environment). When you invoke Cursor through Agent Mode, you'll be asked which credential to use if more than one is connected.

  • Remote MCP Servers — allowlist as many MCP servers as you need; each one is added independently and exposes its own set of tools.

  • Other connectors — the same model applies to all current and future connector types.

Constraints:

  • The Connector Name must be unique across all Destinations in the workspace — including other connector types and Destinations configured under Integrations → Destinations. For example, you cannot reuse prod-alerts as both a Slack App connector name and a PagerDuty Destination name.

  • For connectors bound to an external workspace (such as Slack), each instance is bound to one workspace; you cannot reuse the same workspace across two instances.

  • For personal credentials (such as Cursor), there is no upper limit on how many you can add to your account.

Available Connectors

Connector
Description

Slack

Integrate with Slack for monitor notifications and agent interactions via @mentions

Linear

Create and manage Linear issues from monitors, Notification Routes, and Agent Mode

Cursor Cloud Agents

Run Cursor's cloud coding agent on your repositories directly from Agent Mode

Claude Managed Agents

Run coding tasks using a Claude agent and environment configured in Anthropic

Notion

Search workspace knowledge and publish investigation findings

Pylon

Investigate customer issues and take support actions

GitHub

Investigate code and manage issues, pull requests, and development work

PagerDuty

Investigate and manage incidents, services, schedules, and on-call work

Rootly

Investigate incidents and coordinate response and follow-up work

incident.io

Analyze operations and manage incidents, escalations, and follow-ups

Atlassian Rovo

Read and update Jira issues and Confluence knowledge

Remote MCP Servers

Allowlist custom MCP servers with token or OAuth authentication

Managing Connectors

The Connectors page has two tabs:

  • My Connections — where any user can link their personal account for an enabled connector

  • Org Connectors — where admins enable connector types and configure org-level credentials (e.g., the Slack App)

For Admins

Go to Integrations → Connectors and open the Org Connectors tab to enable or disable connector types for your organization, and to configure org-level credentials where required (e.g., the Slack App). Disabling a connector does not delete existing user credentials, but prevents them from being used until re-enabled.

For Users

Once a connector is enabled by an admin:

  1. Go to Integrations → Connectors → My Connections

  2. Select the connector you want to set up

  3. Authorize your account or provide your credentials, then configure any defaults

  4. When you ask Agent Mode to use a specific tool (e.g., "use Cursor to fix the failing test"), it will use your connected credentials to perform the action

You can update your credentials, change configuration, or disconnect at any time from the same page.

Next Steps

Last updated