composio

Composio Plugin For Claude

Connect Claude Code to Composio's hosted MCP server:

https://connect.composio.dev/mcp

Composio gives Claude one connection to 1000+ apps, including Gmail, Slack, GitHub, Linear, Notion, HubSpot, Google Calendar, Figma, Google Sheets, Salesforce, Jira, Sentry, Datadog, and more. Use it when you want Claude to stop at chat and act across the tools you already use.

What This Plugin Adds

• .claude-plugin/plugin.json: Claude Code plugin metadata and component paths.
• .mcp.json: an HTTP MCP server named composio that points at https://connect.composio.dev/mcp.
• skills/composio/SKILL.md: guidance for when Claude should use Composio, how to handle multi-app workflows, and when to ask for confirmation.

Example Workflows

• Draft a weekly update from Linear issues and Slack threads.
• Summarize blocked GitHub PRs and ping reviewers in Slack.
• Pull Figma review comments into a Notion design doc.
• Draft Gmail follow-ups after demos and log notes in HubSpot.
• Schedule Google Calendar meetings and send a Slack heads-up.
• Triage Sentry or Datadog alerts and create follow-up GitHub or Linear issues.

Local Development

From this repository, run Claude Code with the plugin directory:

claude --plugin-dir .

Then verify that the MCP server is loaded:

/mcp

Select Composio in the MCP server manager and complete the browser authentication flow if prompted. After authentication, Composio tools will be available through Claude Code's MCP tool system.

Claude Tag In Slack

Claude Tag in Slack is admin-managed. It does not use a developer's local Claude Code plugin install or personal Claude connectors in shared channels.

To make Composio work with @Claude in Slack, an organization Owner should configure it through Claude Tag Access bundles:

1. Open claude.ai/admin-settings/claude-tag.
2. Pair the Slack workspace if Claude Tag is not already enabled.
3. Create or open the Access bundle for the workspace or Slack channel where Composio should be available.
4. In the bundle's Plugins tab, attach this plugin, or add it from the organization's skills/plugin repository. The plugin is what declares the Composio MCP server through .mcp.json.
5. In the bundle's Credentials tab, click Connect another app and add a credential for connect.composio.dev.
6. If using a Composio consumer API key, send it as the x-consumer-api-key header and restrict the allowed website to connect.composio.dev.
7. Test in a private Slack channel by inviting @Claude and asking it to use Composio for a read-only task first.

Important Claude Tag behavior:

• Access is scoped by workspace, channel, or organization. Attach Composio only to the channels that need it.
• Channel access uses Claude Tag's agent identity, not the personal connector of the user who tagged Claude.
• A .mcp.json sitting in a repository Claude clones is not loaded by Claude Tag. The MCP server must be declared by an attached plugin.
• New or changed plugins and credentials apply to new Slack threads. Start a fresh thread after changing Access bundle settings.

Authentication

The default plugin config uses Claude Code's HTTP MCP OAuth flow and does not store secrets in the repository. Claude should not ask users to paste app passwords, personal access tokens, or .env secrets for apps that can connect through Composio OAuth.

If your environment requires a Composio consumer API key, configure a user-level or project-level MCP server override:

claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp --header "x-consumer-api-key: YOUR_API_KEY"

Claude Code gives user and project MCP servers precedence over plugin-provided servers, so this override will take priority.

Safety Model

Composio keeps auth, scopes, and connected accounts on Composio's side. The bundled skill tells Claude to:

• Ask which app, workspace, project, repository, channel, or account to use when the target is ambiguous.
• Use the narrowest MCP tool that completes the task.
• Treat connected account data as private and retrieve only what is needed.
• Ask for confirmation before sending, publishing, deleting, granting access, moving money, or changing production systems.

Publishing

The plugin is already structured with the required .claude-plugin/plugin.json manifest at the plugin root. To publish it, host this repository and add it as a Claude Code plugin marketplace or install it directly from the plugin directory during development.