---
title: Connectors
description: Connect Olly to Jira, Sentry, PagerDuty, and other tools your team works in, and control which of their tools Olly can call on your behalf.
url: https://coralogix.com/docs/user-guides/olly/connectors/
product: ai
feature: Olly
feature_id: olly
feature_identifier: ai/olly
last_updated: '2026-11-10'
---

# Connectors

Connect Olly to the tools your team already works in, so it can pull context from them during an investigation. Most connectors reach a tool through its Model Context Protocol (MCP) server; the [GitHub](#github) connector uses the GitHub integration instead.

Every connection is personal. Olly acts with your credentials and reaches only what your own account in that tool can reach, so connecting a tool does not expose it to your teammates. You decide which of the tool's capabilities Olly may call.

Public beta

Connectors are in public beta and not yet available to every team. To request access, contact your account representative or Support.

## What you need

* Connectors available for your team. They are on by default, but an admin can turn them off for the whole team or one connector at a time. See [Turn connectors on or off for your team](#turn-connectors-on-or-off-for-your-team).
* An account in the tool you want to connect, with access to the projects or repositories you expect Olly to read.
* For a tool that signs in with an API key, a token you generate in that tool.

## Available connectors

| Connector         | Sign-in   | What Olly uses it for                                                                  |
| ----------------- | --------- | -------------------------------------------------------------------------------------- |
| GitHub            | OAuth 2.0 | Repository code, to trace logs, errors, and alerts to the exact files and lines        |
| GitLab            | OAuth 2.0 | Issues, merge requests, and projects, cited in Olly's answers                          |
| Jira & Confluence | OAuth 2.0 | Issues, sprints, and Confluence runbooks, to correlate production signals with tickets |
| PagerDuty         | API key   | Incidents, on-call schedules, and services, to enrich an alert investigation           |
| Sentry            | OAuth 2.0 | Stack traces, releases, and suspect commits behind an error spike                      |
| Linear            | OAuth 2.0 | Issues, projects, and cycles, cited in Olly's answers                                  |
| Notion            | OAuth 2.0 | Runbooks, postmortems, and design docs, so Olly can cite your team's written procedure |

[![Olly AI Connectors page with the GitHub card first, followed by GitLab, Jira, PagerDuty, Sentry, Linear, Notion, and coming-soon Wiz and JFrog](/docs/assets/images/connectors-available-e05cae34802683c9f3fa5e96677d8fde.webp)](https://coralogix.com/docs/assets/images/connectors-available-e05cae34802683c9f3fa5e96677d8fde.webp)

Shows the Olly AI Connectors page with the GitHub card as the first connector.

### Coming soon

Connectors for JFrog and Wiz are on the way. You cannot connect them yet.

## GitHub

GitHub connects through the GitHub integration, the app Coralogix installs in your GitHub organization, rather than an MCP server. An organization has one GitHub integration shared by the whole team, so GitHub connects and disconnects differently from the other connectors:

* Installing the app in a GitHub organization is a GitHub organization-owner action. A repository admin can start the installation, but a GitHub organization owner approves it.
* **Connect** installs the app, or authorizes your repositories when the app is already installed, then returns you to the connectors page. The card shows **Connected** once the app is installed and your repositories are authorized.
* Olly uses GitHub for repository context, so there is no tool authorization step, and the GitHub card has no on/off switch.
* **Disconnect** removes your repository access from Olly. The app stays installed in the organization for the rest of your team.
* Connecting the GitHub card is how each user connects their own GitHub account. Once you are connected, **Select repo** appears in the **+** menu of the Olly chat input, so you can pick the repository Olly uses for the chat.

For the installation steps, the GitHub permissions involved, and how to request access to specific repositories, see [GitHub](https://coralogix.com/docs/user-guides/olly/github.md).

## Connect a tool

1. In Coralogix, select **Olly AI** in the navigation bar, then **Connectors**.

2. Find the tool you want and select **Connect**.

3. Complete the sign-in for that tool:

   <!-- -->

   * **OAuth 2.0**: Coralogix sends you to the tool's sign-in page. Approve the request and you return to the connectors page.
   * **API key**: generate a token in the tool, then paste it into the dialog box and confirm. Each connector links to the page in its own documentation that explains where to generate the token.

4. Review the tools Olly may call, then select **Save**.

Olly starts using the connection on your next message.

## Choose which tools Olly can call

Each connected tool exposes its own set of tools, and you control which ones Olly is allowed to call. Select **Manage tools** on a connection to open the list. The card shows how many of the available tools you have authorized.

Tools are grouped by what they can do:

* **Read-only**: tools that only read data. These are authorized automatically when you connect.
* **Write / delete**: tools that create, change, or delete data in the connected system. These stay off until you turn them on.

A tool counts as read-only only when its server explicitly declares it as such. Anything the server leaves unlabeled is grouped with write and delete tools, so a tool whose effect Coralogix cannot confirm stays off until you authorize it deliberately.

Note

Authorizing a write or delete tool lets Olly change data in that system using your credentials. Turn on only the tools you want Olly to act with.

## Check a connection's status

Each connector shows one of three states:

* **Connected**: Olly can use the tool. The card also shows when the connection was last validated.
* **Not connected**: no connection exists yet.
* **Reconnect needed**: Olly can no longer authenticate with the tool, so it cannot use the connection until you reconnect.

Connections whose connector is no longer offered appear separately under **Other connections**, where you can still review their tools or disconnect them.

## Turn a connection on or off

Each MCP connection has an on/off switch, so you can stop Olly from using a tool without disconnecting it. Turning a connection off keeps its credential and your tool selection. Turn it back on to let Olly use it again.

The switch appears in two places:

* On the connector card on the **Connectors** page, next to the status.
* In the Olly chat input: select **+**, then **Connectors**. The submenu lists your connected tools, each with its switch. Hover the info icon next to a tool to see what Olly uses it for. **Manage connectors** opens the **Connectors** page.

[![A connected Notion card on the Connectors page with the Connected status and the on/off switch turned on, 40 of 78 tools authorized, Manage tools, and Disconnect](/docs/assets/images/connector-card-toggle-bd8c68750c9c1f26241f99a89807f8d7.webp)](https://coralogix.com/docs/assets/images/connector-card-toggle-bd8c68750c9c1f26241f99a89807f8d7.webp)

The switch is unavailable while an admin has [turned connectors off for your team](#turn-connectors-on-or-off-for-your-team). A connection that needs reconnecting shows a warning icon in the chat submenu; select it to open the **Connectors** page.

## Reconnect a tool

Select **Reconnect** on a connection that needs it, then confirm. Reconnecting removes the current connection along with your tool selection, then takes you through the sign-in again, so review the tools afterward.

## Disconnect a tool

Select **Disconnect** on the connection and confirm. Olly loses access to the tool and the stored credential is deleted. To use the tool again, connect it again from the connectors page.

## Turn connectors on or off for your team

Connectors are available to every team by default. An admin can turn them off for the whole team on the AI settings page, alongside the setting that controls whether Olly can reach the public internet. See [AI settings](https://coralogix.com/docs/user-guides/olly/ai-settings.md).

1. Select **Olly AI** in the navigation bar, then **AI Settings**.
2. Turn **Enable Connectors** on or off.

While the setting is off, the connectors page shows a banner that an admin turned connectors off, and **Connect** and **Reconnect** are unavailable. Members cannot add a connection and Olly cannot use the ones they already made. Those connections stay listed, and members can still review their tools or disconnect them, so turning the setting back on restores what your team already configured.

An admin can also turn off one connector and leave the rest on, from **Connectors your team can use** on the same page. A connector turned off this way carries an orange **Disabled by Admin** badge on its card, and its **Connect**, **Reconnect**, **Manage tools**, and enable controls are unavailable. A member who already connected that tool keeps the connection set up, and it works again once an admin turns the connector back on. The GitHub integration is set up separately and has no per-connector toggle. See [AI settings](https://coralogix.com/docs/user-guides/olly/ai-settings.md).

[![The Olly AI Connectors page with connectors turned off, showing a banner about the admin setting and connector cards whose Connect buttons are unavailable](/docs/assets/images/connectors-disabled-c44e659d8b15bf871d40e6446e2c5b93.webp)](https://coralogix.com/docs/assets/images/connectors-disabled-c44e659d8b15bf871d40e6446e2c5b93.webp)

Shows what members see while connectors are off, with each connector's sign-in method and its connection status.

Each connection belongs to the member who created it, and Olly acts with that member's credentials in the connected tool. Enabling connectors lets members connect their own tools, it does not give Olly access to anything on its own. Members then decide which of a tool's capabilities Olly may call, as described in [Choose which tools Olly can call](#choose-which-tools-olly-can-call).

## Permissions

| Permission                | What it allows                                           |
| ------------------------- | -------------------------------------------------------- |
| `OLLY:SENDMESSAGE`        | Open the connectors page and manage your own connections |
| `TEAM-AI-SETTINGS:MANAGE` | Turn connectors on or off for the whole team             |

See the full list in [Permissions list](https://coralogix.com/docs/user-guides/aaa/access-control/permissions/permissions-list.md).

## Next steps

Review how Olly processes and protects your data in [Data processing, privacy, and compliance](https://coralogix.com/docs/user-guides/olly/data-privacy.md).
