# 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** | **Settings → 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 %}

## Available Connectors

| Connector                                           | Description                                                                   |
| --------------------------------------------------- | ----------------------------------------------------------------------------- |
| [**Cursor**](/use-groundcover/connectors/cursor.md) | Run Cursor's cloud coding agent on your repositories directly from Agent Mode |

{% hint style="info" %}
Connector authentication is currently supported via API keys only.
{% endhint %}

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

## Managing Connectors

### For Admins

Go to **Settings → Connectors** to enable or disable connector types for your organization. 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**
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

* [Cursor](/use-groundcover/connectors/cursor.md) — Set up and use the Cursor connector with Agent Mode


---

# Agent Instructions: 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.