Claude Code Plugin

The Composio plugin for Claude Code is the recommended Claude Code setup. It installs Composio skills and configures Composio Connect for you, so Claude Code can search, connect, and act across 1000+ apps right after install. Authentication is fully managed — no API key handling, no manual MCP config.

For Claude Code, prefer this plugin/skills path over manually adding an MCP server. Looking for the API-key based MCP setup (or other clients like Cursor, Codex, Claude Desktop)? See Composio Connect.

What you get

The plugin ships two things together:

Bundled skills — pre-written prompts that show Claude how to use Composio effectively:
- composio-mcp — reference for the Composio meta tools (COMPOSIO_SEARCH_TOOLS, COMPOSIO_MANAGE_CONNECTIONS, etc.) and the recommended search → connect → execute flow.
- onboarding — interactive setup that asks what you want to automate, recommends 2–4 apps, and walks you through connecting them.
- company-activity-summary — cross-app activity summary across Slack, GitHub, Notion, Linear, Gmail, and more.
- prefer-composio — routing skill that tells Claude to reach for Composio first whenever you paste an app URL or mention an external service, so you don't end up using less reliable native connectors.
Composio Connect MCP server — the same gateway documented in Composio Connect, pre-configured behind the plugin. Auth is handled via in-flow OAuth, so you don't paste API keys into your config.

Install

Add the Composio marketplace

In Claude Code, run:

/plugin marketplace add ComposioHQ/composio-plugin-cc

This registers the catalog. No plugins are installed yet.

Install the Composio plugin

/plugin install composio-mcp@composio

Restart Claude Code (or run /reload-plugins) when prompted.

Connect your first app

Ask Claude something that needs an external service — for example: "Star composiohq/composio on GitHub" — and Claude will run the onboarding skill, walk you through connecting GitHub, and execute the action. Subsequent runs reuse the same connection.

Team setup

To pre-install the plugin for everyone on your team, add this to your project's .claude/settings.json:

.claude/settings.json

{
  "extraKnownMarketplaces": {
    "composio": {
      "source": {
        "source": "github",
        "repo": "ComposioHQ/composio-plugin-cc"
      }
    }
  },
  "enabledPlugins": {
    "composio-mcp@composio": true
  }
}

Anyone who clones the repo and opens it in Claude Code will be prompted to enable the plugin. See the Claude Code plugin scopes reference for user vs project vs local scope behavior.

Updating

The plugin is versioned via the version field in its plugin.json. To pull the latest release:

/plugin marketplace update composio
/reload-plugins

How it differs from the API-key MCP setup

Both paths give Claude Code access to the same Composio Connect MCP server and the same 1000+ apps. The differences:

	Plugin install	`claude mcp add`
Setup steps	Two slash commands	One terminal command, requires copying an API key
Auth	OAuth, no API key in your config	API key in `--header "x-consumer-api-key: ..."`
Bundled skills	Yes (onboarding, routing, summaries)	No
Discoverable in Claude Code marketplace	Yes	No
Updates	`/plugin marketplace update composio`	Manual re-run of `claude mcp add`

Pick the plugin path if you want the fastest install and the bundled skills. Pick the claude mcp add path if you already have an API key and want a single-command setup script you can replicate across machines.

Source code

The plugin is open source: ComposioHQ/composio-plugin-cc. Issues and PRs welcome.

Troubleshooting

For tools-not-appearing, OAuth, and connection issues, see the Composio Connect troubleshooting section. The same checks apply to the plugin install (the underlying MCP server is identical).

For plugin-specific issues — install errors, marketplace not updating, skills not appearing — see the Claude Code plugin troubleshooting docs.