composio-mcp

# Composio — CLI (primary) + MCP (fallback) Connect AI agents to 1000+ external apps through Composio. This skill covers **two execution paths** and the full tool surface. | Path | Transport | Auth | When to use | |------|-----------|------|-------------| | **A. CLI (primary)** | `composio` binary on PATH | `ak_*` project API key | Headless servers, scripts, any agent with shell access. Works once `composio login` succeeds. | | **B. MCP (fallback)** | HTTP `https://connect.composio.dev/mcp` | `ck_*` consumer key in `x-consumer-api-key` | MCP-native agents that prefer tool calls over shell. Needs the consumer key from the dashboard. | Both paths talk to the same Composio backend and expose the same toolkits. The CLI is the path of least resistance on headless boxes because it ships its own auth (`composio login`). ## Decision flow ``` Need to use Composio? ├─ Agent has shell access? → Use CLI (Path A) → composio search/execute/link/run/proxy └─ Agent is MCP-native only? → Use MCP (Path B) → mcp__composio__* tool calls ``` **CLI fallback pattern:** When the MCP server is down or unconfigured, the CLI can perform every operation the MCP would do — `composio execute` replaces MCP tool calls, `composio search` replaces MCP search, `composio link` replaces MCP auth flows. ## When to use - `devin mcp list` / `claude mcp list` shows `composio` **failing to list tools** (auth error). - The user says "configure Composio", "Composio MCP not working", "composio auth failed". - A ...