> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/use-groundcover/connectors.md).

# Connectors

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](/use-groundcover/agent-mode.md) 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.

{% hint style="info" %}
The PagerDuty, Rootly, and incident.io connector cards give **Agent Mode** access to those services. To send monitor notifications, configure a [PagerDuty](/integrations/connected-apps/pagerduty.md), [Rootly](/integrations/connected-apps/incident.io-1.md), or [incident.io](/integrations/connected-apps/incident.io.md) Destination instead.
{% endhint %}

## 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](/use-groundcover/connectors/linear.md) or [Slack](/use-groundcover/connectors/slack.md) 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.

{% hint style="info" %}
Admin permissions are required to enable or disable a connector for the organization.\
Any workspace member with [Agent Mode access](/use-groundcover/agent-mode/privacy-and-security.md) can connect their own account once the connector is enabled.
{% endhint %}

<div data-with-frame="true"><figure><img src="/files/dmcbwQUz43o38opidlPv" alt="Connector list in groundcover"><figcaption><p>Connectors are available as first-class cards under Integrations → Connectors.</p></figcaption></figure></div>

## 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](/use-groundcover/connectors/slack.md#selecting-slack-channels-in-notification-routes), 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**](/use-groundcover/connectors/slack.md)                                 | Integrate with Slack for monitor notifications and agent interactions via @mentions |
| [**Linear**](/use-groundcover/connectors/linear.md)                               | Create and manage Linear issues from monitors, Notification Routes, and Agent Mode  |
| [**Cursor Cloud Agents**](/use-groundcover/connectors/cursor.md)                  | Run Cursor's cloud coding agent on your repositories directly from Agent Mode       |
| [**Claude Managed Agents**](/use-groundcover/connectors/claude-managed-agents.md) | Run coding tasks using a Claude agent and environment configured in Anthropic       |
| [**Notion**](/use-groundcover/connectors/notion.md)                               | Search workspace knowledge and publish investigation findings                       |
| [**Pylon**](/use-groundcover/connectors/pylon.md)                                 | Investigate customer issues and take support actions                                |
| [**GitHub**](/use-groundcover/connectors/github.md)                               | Investigate code and manage issues, pull requests, and development work             |
| [**PagerDuty**](/use-groundcover/connectors/pagerduty.md)                         | Investigate and manage incidents, services, schedules, and on-call work             |
| [**Rootly**](/use-groundcover/connectors/rootly.md)                               | Investigate incidents and coordinate response and follow-up work                    |
| [**incident.io**](/use-groundcover/connectors/incident-io.md)                     | Analyze operations and manage incidents, escalations, and follow-ups                |
| [**Atlassian Rovo**](/use-groundcover/connectors/atlassian-rovo.md)               | Read and update Jira issues and Confluence knowledge                                |
| [**Remote MCP Servers**](/use-groundcover/connectors/mcp.md)                      | 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

* [Slack](/use-groundcover/connectors/slack.md): Set up the Slack App connector and link your personal account
* [@groundcover Agent in Slack](/use-groundcover/connectors/slack/slack-agent.md): Use the groundcover Agent directly from Slack via @mentions
* [Linear](/use-groundcover/connectors/linear.md): Connect a Linear workspace for monitor issues, Notification Routes, and Agent Mode
* [Cursor Cloud Agents](/use-groundcover/connectors/cursor.md): Set up and use the Cursor connector with Agent Mode
* [Claude Managed Agents](/use-groundcover/connectors/claude-managed-agents.md): Connect a Claude agent, environment, vaults, and memory store
* [Notion](/use-groundcover/connectors/notion.md), [Pylon](/use-groundcover/connectors/pylon.md), [GitHub](/use-groundcover/connectors/github.md), [PagerDuty](/use-groundcover/connectors/pagerduty.md), [Rootly](/use-groundcover/connectors/rootly.md), [incident.io](/use-groundcover/connectors/incident-io.md), and [Atlassian Rovo](/use-groundcover/connectors/atlassian-rovo.md): Set up each first-class connector and explore Agent Mode examples
* [Remote MCP Servers](/use-groundcover/connectors/mcp.md): Allowlist custom MCP servers with token or OAuth authentication and manage tool restrictions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/use-groundcover/connectors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.