Skip to main content
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.
Plugins are different from the workspace integrations in Settings → Integrations. 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

Knowledge and documents

Meetings and notes

CRMs

Issue trackers

Incident management

Observability

Product analytics and feature flags

Payments and billing

Slack

Slack isn’t listed on the plugins page. Connect it from Agents → Sidekick Agent → Slack, which also sets up Sidekick Agent in Slack, 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 for which actions ask for approval by default.