> 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 are personal integrations that link groundcover to your external tools (such as Cursor). Once connected, [Agent Mode](/use-groundcover/agent-mode.md) can perform actions in those tools using your credentials, like launching code changes, creating pull requests, or managing tasks.

## Connectors vs Connected Apps

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

| Aspect             | Connectors                                                                | Connected Apps                                                         |
| ------------------ | ------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Scope**          | Personal, each user connects their own account                            | 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 provides their own API key                                           | Admin provides org-wide credentials (webhook URLs, routing keys, etc.) |
| **Used by**        | groundcover Agent Mode during conversations                               | Notification Routes, Monitors, and Workflows                           |
| **Setup location** | **Integrations → Connectors**                                             | **Settings → Connected Apps**                                          |

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

## How It Works

Connectors use a two-tier model:

1. **Organization enablement**: A workspace admin enables a connector type for the organization. This does not require any credentials; it simply makes the connector available to users.
2. **User connection**: Individual users provide their own credentials (e.g., an API key) to connect their personal account. Agent Mode uses these credentials 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 %}

## 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.
* **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 Connected Apps in the workspace — including other connector types and Connected Apps configured under **Integrations → Destinations**. For example, you cannot reuse `prod-alerts` as both a Slack App connector name and a PagerDuty Connected App 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 |
| [**Cursor**](/use-groundcover/connectors/cursor.md)          | Run Cursor's cloud coding agent on your repositories directly from Agent Mode       |
| [**Remote MCP Servers**](/use-groundcover/connectors/mcp.md) | Allowlist Remote MCP Servers to extend Agent Mode with custom tools                 |

Additional connectors, including Linear, Jira, GitHub Copilot, Claude, and more, are coming soon.

## 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. Provide your credentials and configure 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
* [Cursor](/use-groundcover/connectors/cursor.md): Set up and use the Cursor connector with Agent Mode
* [Remote MCP Servers](/use-groundcover/connectors/mcp.md): Allowlist Remote MCP Servers 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:

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

The question should be specific, self-contained, and written in natural language.
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.