> ## Documentation Index
> Fetch the complete documentation index at: https://www.plain.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect plugins to the Sidekick Agent

> Connect plugins such as Linear, GitHub, Datadog, Stripe, or your own MCP server so the Sidekick Agent can look things up and act in your tools.

A plugin is a tool the Sidekick Agent can use, such as Linear, GitHub, Datadog, or Stripe. Some plugins are built by Plain, and others connect to a vendor's Model Context Protocol (MCP) server, but you connect them all the same way from **Agents → Sidekick Agent → Plugins**. This page covers the plugins you can connect, how to connect them, and how to add your own MCP server. For what the Sidekick Agent can do in these tools, and how approvals work, see [Actions and approvals](https://www.plain.com/docs/product/agents/sidekick/actions-and-approvals.md).

> [!NOTE]
>
> Plugins are different from the workspace integrations in [**Settings → Integrations**](https://www.plain.com/docs/product/integrations.md). Workspace integrations sync data into Plain, add channels, and link threads to Linear or Jira issues. Plugins are the tools the Sidekick Agent calls while it works.

## Find a plugin

The plugins page groups plugins by category. Plain's own tools sit at the top under **Built in** and are always on. Your own MCP servers sit at the bottom under **Custom**.

To narrow the list:

* **Search**: type a plugin's name, a category such as `observability`, or what it covers, such as `billing`. Search tolerates typos
* **All plugins or Connected**: switch to **Connected** to see only the plugins your workspace has set up

## Connect a plugin

You need to be a workspace **Admin** or **Owner** to connect plugins. A connection is shared with everyone in your workspace as soon as you connect it.

**1. Open the plugins page**

Go to **Agents → Sidekick Agent → Plugins**.

**2. Pick a plugin**

Find the plugin you want and click **Connect**.

**3. Authorize access**

Sign in to the tool, or enter the API key or region it asks for, then click **Connect for workspace**. The table for each category below lists what each plugin needs.

A connected plugin shows a **Connected** badge. To disconnect it, open it from the plugins page and disconnect it there.

## How plugins work in a session

You don't configure anything per session. When you open the Sidekick Agent, it discovers which plugins your workspace has connected and uses them as needed. As it works, you can see its tool calls on screen in real time, so you always know what it looked up and why.

## Available plugins

Every plugin is opt-in. Plugins that connect to a vendor's MCP server get their tools from that server, so the vendor decides what the Sidekick Agent can do there. Where a plugin asks for a region, pick the one your account is hosted in.

### Repos and code

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **GitHub** | Search code and repository context | Install the GitHub app |
| **GitLab** | Issues, merge requests, and code on GitLab.com | OAuth. For self-managed GitLab, [add your own MCP server](#add-your-own-mcp-server) |
| **WorkOS** | An organization's SSO, directory sync, and users | OAuth |
| **Braintrust** | AI traces, experiments, and evals | OAuth, with a US or EU region |
| **Tinybird** | Your Tinybird data sources and endpoints | API key: a static token from **Tinybird → Tokens**, entered as `Bearer your_tinybird_token`. An admin token exposes every tool |

### Knowledge and documents

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **Notion** | Search pages and databases for documentation and runbooks | OAuth |
| **Confluence** | Your Confluence pages and spaces | OAuth |
| **Dropbox** | Files and folders in Dropbox | OAuth |

### Meetings and notes

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **Granola** | AI meeting notes and summaries | API key |
| **Grain** | Meeting recordings, transcripts, and call summaries | API key |
| **Gong** | Insights from sales calls and emails for an account or deal | OAuth. A Gong tech admin must first add an MCP server integration with automatic registration in Gong |
| **Sybill** | Sales calls, deals, and account insights | OAuth |

### CRMs

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **HubSpot** | Contacts, companies, and deals; ticket status and pipeline stage; CRM activity and owner details | OAuth. Listed only for workspaces that have already connected it |
| **Attio** | Company and contact records by email or domain; pipeline stages; account notes and tasks | OAuth |
| **Close** | Leads, contacts, opportunities, and activity | OAuth |
| **Pipedrive** | Deals, contacts, organizations, and activities | OAuth |

### Issue trackers

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **Linear** | Search issues, look up status, find related projects and cycles | OAuth |
| **Jira** | Search issues with JQL, look up issue details and comments | OAuth. To connect without a personal Atlassian login, see [Connect Jira](https://www.plain.com/docs/product/agents/sidekick/plugins/jira.md) |
| **Shortcut** | Stories, epics, and iterations | OAuth |

### Incident management

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **incident.io** | List active incidents, get incident details | API key |
| **Rootly** | Active incidents, timelines, and on-call | OAuth |
| **OneUptime** | Incidents, monitors, and status pages | OAuth |
| **OpenStatus** | Monitors, incidents, and status page updates | OAuth |

### Observability

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **Datadog** | Query metrics, logs, and monitor status | API key |
| **Grafana** | Query dashboards and production signals | Service account token |
| **Sentry** | Look up errors and exceptions, find related events | API key |
| **New Relic** | Errors, alerts, and performance data | OAuth, with a US, EU, or Japan region |
| **Honeycomb** | Traces, errors, and service health | OAuth, with a US or EU region |

### Product analytics and feature flags

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **PostHog** | Product events, session recordings, and user analytics; what a user has done in the product | Personal API key |
| **LaunchDarkly** | Feature flag status and targeting rules, rollout percentages, which variation is active per environment | API key |
| **Amplitude** | Events, charts, cohorts, and product usage | OAuth, with a US or EU region |
| **Mixpanel** | Events, reports, and how customers use your product | OAuth, with a US, EU, or India region |
| **Pendo** | Product usage, guides, and feedback for an account | OAuth, with a US, US1, EU, Japan, or Australia region |

### Payments and billing

| **Plugin** | **What the Sidekick Agent can look up** | **How you connect** |
| - | - | - |
| **Stripe** | Customers, subscriptions, invoices, and payments | OAuth |
| **Hyperline** | Customers, subscriptions, invoices, and usage | OAuth, with a **Live** or **Sandbox** environment |
| **Paddle** | Customers, subscriptions, and transactions | OAuth |
| **Orb** | Customers, subscriptions, invoices, and usage | API key, entered as `Bearer your_orb_api_key` |
| **Recurly** | Recurly's documentation and API reference. Recurly's MCP server is in early access and can't read your site's billing data yet | OAuth |

### Slack

| **Plugin** | **What the Sidekick Agent can look up** |
| - | - |
| **Slack** | Search channels and messages, look up users |

Slack isn't listed on the plugins page. Connect it from **Agents → Sidekick Agent → Slack**, which also sets up [Sidekick Agent in Slack](https://www.plain.com/docs/product/agents/sidekick/in-slack.md), so your team can @mention Plain inside a Slack channel.

## Add your own MCP server

You can connect any internal tool or a vendor that isn't listed through your own MCP server. The server must accept MCP over HTTP.

**1. Open the Add MCP server form**

Go to **Agents → Sidekick Agent → Plugins**, then in **Custom** click **Add MCP**.

**2. Fill in the server details**

* **Name**: the name your team sees, such as `Acme internal tools`
* **Server URL**: the server's HTTP endpoint
* **Authentication**: **OAuth** if the server signs you in, or **API key** if it takes a static key or token

**3. Add auth parameters for an API key**

For **API key**, add each parameter the server expects under **Auth parameters**. Set its placement to **Header** or **Query**, its name, and its value, for example an `Authorization` header with the value `Bearer your_api_key_here`.

**4. Connect the server**

Click **Connect for workspace**. For OAuth, sign in to the server to authorize access.

The server appears under **Custom** with the tools it lists. If its URL is on the same host as a plugin in the list, it appears under that plugin instead, with the plugin's name and logo. Your workspace can have up to 10 MCP servers, including the ones behind connected plugins.

## Tool permissions

Each plugin gives the Sidekick Agent a set of tools, and each tool has its own approval setting. Open a connected plugin from the plugins page to set each tool to **Always allow**, **Ask**, or **Disable**. Plugins built by Plain also have a **Custom instructions** section, for guidance on how the Sidekick Agent should use that tool. See [Actions and approvals](https://www.plain.com/docs/product/agents/sidekick/actions-and-approvals.md) for which actions ask for approval by default.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.