Skip to main content
Plugins bundle capabilities such as skills, MCP servers, and connected apps. Open Plugins from a Claude or Codex space. The catalog follows the selected provider. Copilot and Cursor do not currently expose a plugin catalog in Mains.

​
Browse the catalog

Search plugins or browse their categories. Open a plugin to inspect its description, source, included skills, apps, MCP servers, and setup state. The Installed shelf shows your installed plugins. Installation and authentication are separate: a plugin can be installed while one of its included apps still needs setup. Unavailable installs display a reason. Catalog contents and access policies depend on the provider and your account.

​
Install and connect

1

Inspect the plugin

Read what it includes and which services it can access.
2

Install

Use the install control. For Claude, choose the supported user, project, or local scope.
3

Complete included app setup

Follow any connection or sign-in actions shown on the detail page.
4

Start a conversation

Use a new run so its provider can discover the updated capabilities. Select an available plugin or skill from the composer when you want to invoke it explicitly.
You can enable or disable plugins where the provider supports that operation, or uninstall them from their detail page.

​
Interactive apps

Codex plugins can provide MCP apps that open beside the conversation or from the rail. A connected service’s tools can still work when its interactive UI is not compatible with the host.

​
Plugins, skills, and Connections

Connecting GitHub in Settings does not automatically install a GitHub plugin. Installing a plugin does not configure every Mains connection.