Composio MCP setup

Connect Composio so an AI client can call tools against apps you already use—Gmail, GitHub, Vercel, Slack, and many more—without hand-rolling OAuth for each one.

For where this sits in the stack, see Composio and MCP connectors. For how the Cursor install ladder works as a reusable pattern, see Studio MCP install strategies.

Official client matrix (source of truth for URLs)

Composio onboarding setup

Cursor

  1. Install the marketplace plugin: cursor.com/marketplace/composio

  2. Or add a user MCP server in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

  1. Complete Composio OAuth when Cursor prompts (mcp_auth / browser).

  2. Start a new agent chat so the MCP catalog refreshes.

  3. Prefer the Composio search tool first (COMPOSIO_SEARCH_TOOLS), then execute app tools through the multi-execute helper. Do not invent tool slugs.

On Windows, writing mcp.json is more reliable than cursor --add-mcp from PowerShell (quote stripping).

Terminal agents (CLI)

Claude Code, Codex, Hermes, OpenClaw, and similar shells use the Composio CLI:

curl -fsSL https://composio.dev/install | sh
composio login

Other MCP clients

Any client that speaks MCP over streamable HTTP can use:

Examples:

gemini mcp add --scope user --transport http composio https://connect.composio.dev/mcp

Clients without OAuth support: see Composio clients.

Connect apps you need

Composio MCP auth is not the same as app auth. After the server is Active:

  1. Search tools for the workflow (e.g. “fetch Gmail about failed CI”, “list Vercel deployments”).

  2. If a toolkit shows no active connection, call the manage-connections flow and open the returned link.

  3. Wait until the connection is Active before executing that toolkit’s tools.

Typical starter set for “CI emails → fix → clear”:

  • Gmail — find failure / expired / needs-attention mail; mark read when done

  • GitHub — Actions runs, logs, re-runs (optional if you already use gh in the shell)

  • Vercel (or your host) — deployment events and project scope

Smoke test: CI mail triage

Once Gmail is connected, run a real tool call before calling setup “done”:

  1. Search / fetch recent mail about failed workflows, expired checks, or deploy errors.

  2. Open the linked run or deployment; fix or re-run until green when that is the right move.

  3. Mark addressed threads read (or archive) so the same alert does not linger.

  4. After you push a fix, wait briefly and re-check the inbox for new failure mail.

That loop is the intended product use—not “MCP listed in settings.”

Related