Composio

Composio

Use this skill when a user asks Claude Code to act in third-party apps through Composio. Composio gives Claude one connection to 1000+ apps, including Gmail, Slack, GitHub, Linear, Notion, HubSpot, Google Calendar, Figma, Google Sheets, Salesforce, Jira, Sentry, Datadog, Discord, and other Composio-supported integrations.

Composio is most useful when the user wants to stop at chat and have Claude do the work: search inboxes, summarize work, draft updates, create issues, schedule meetings, update docs, triage alerts, or coordinate workflows across multiple apps.

MCP Server

This plugin provides the composio MCP server:

{
  "type": "http",
  "url": "https://connect.composio.dev/mcp"
}

After the plugin is installed and loaded, run /mcp in Claude Code to confirm the Composio server is enabled and complete the browser authentication flow if prompted.

When To Use

Prefer Composio MCP tools when the task involves:

1. Reading, searching, or summarizing data from connected apps.
2. Creating or updating records in tools like GitHub, Linear, Notion, HubSpot, Jira, Google Sheets, or Salesforce.
3. Sending messages, emails, calendar invites, or workflow updates through apps like Slack, Gmail, Outlook, or Google Calendar.
4. Combining context across apps, such as Linear issues plus Slack threads, GitHub PRs plus reviewer pings, or Figma comments plus Notion docs.
5. Working with multiple accounts for the same app, such as work, personal, and team email accounts.

Common workflows:

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

Operating Rules

1. If authentication is missing, ask the user to open /mcp, select Composio, and complete the OAuth flow.
2. Ask which app, workspace, project, channel, repository, or account to use when the target is ambiguous.
3. Before taking actions with side effects, state the action and use the narrowest MCP tool that completes the task.
4. For destructive, irreversible, or externally visible operations, ask for confirmation before calling the MCP tool.
5. Prefer scoped access and least privilege. Do not ask for passwords or raw app tokens when OAuth through Composio is available.
6. Treat connected account data as private. Only retrieve or expose the data needed for the user's current task.
7. If a workflow spans multiple apps, complete it step by step and summarize what changed in each app.

Account And Safety Model

Composio keeps auth, scopes, and connected accounts on Composio's side. Claude should not ask users to paste app passwords, personal access tokens, or .env secrets for supported OAuth apps.

When multiple connected accounts are available, disambiguate before acting. Examples include choosing between work email, personal email, and team inboxes, or selecting the correct Slack workspace or GitHub organization.

Use guardrails for potentially risky actions:

1. Read-only actions usually do not need confirmation.
2. Drafting content is safe when the draft is not sent or published.
3. Sending, publishing, deleting, granting access, moving money, or changing production systems requires explicit confirmation.

API Key Option

The default plugin configuration uses browser-based OAuth through Claude Code. For environments that require a consumer API key instead, configure a user-level or project-level MCP server with this header:

{
  "mcpServers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp",
      "headers": {
        "x-consumer-api-key": "${COMPOSIO_API_KEY}"
      }
    }
  }
}

Claude Code gives user and project MCP servers precedence over plugin-provided MCP servers, so this override can coexist with the plugin.