Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | # Composio For You |
| 2 | |
| 3 | Use this product when someone wants their own AI client or terminal agent to use their own connected apps. Route by task: answer a question, configure an MCP client, operate through the CLI, connect an app, or debug an existing setup. |
| 4 | |
| 5 | ## Stable product contract |
| 6 | |
| 7 | - MCP endpoint: `https://connect.composio.dev/mcp` |
| 8 | - Consumer key when a client needs a header: `ck_...` |
| 9 | - Header name: `x-consumer-api-key` |
| 10 | - Key location: Dashboard → For You → AI Clients → select the client |
| 11 | |
| 12 | The removed `mcp.composio.dev` endpoint and Platform MCP URLs are not substitutes. The `ck_...` key and Platform's `COMPOSIO_API_KEY` are not interchangeable. |
| 13 | |
| 14 | ## Choose MCP or CLI |
| 15 | |
| 16 | Default to MCP for desktop and hosted AI clients. Use the CLI for terminal agents that can execute commands and operate tools directly. |
| 17 | |
| 18 | ### Know what each surface installs |
| 19 | |
| 20 | These surfaces are complementary. Installing one does not automatically install the others. |
| 21 | |
| 22 | | Surface | What the agent discovers | |
| 23 | |---|---| |
| 24 | | Raw Composio MCP connection | Callable tools and their schemas. MCP does not install an agent skill. | |
| 25 | | Public `composio` skill | This product-and-job router. Install it explicitly from `ComposioHQ/composio`. | |
| 26 | | Composio CLI | The `composio` command plus the separately maintained `composio-cli` skill when the CLI's agent setup flow installs it. That skill owns current command usage. | |
| 27 | | OpenAI/Codex plugin | The hosted Composio app plus its bundled `composio-runtime` skill, which selects between hosted tools and the local CLI. | |
| 28 | | Claude Code plugin | Commands and hooks. It does not bundle a skill; CLI login/setup installs `composio-cli` separately. | |
| 29 | |
| 30 | An agent can therefore see Composio tools without seeing either Composio skill, and it can have more than one skill when their roles differ. Use `composio` for product selection and integration guidance, `composio-runtime` for OpenAI plugin routing, and `composio-cli` for CLI operation. |
| 31 | |
| 32 | ### MCP clients |
| 33 | |
| 34 | Claude Desktop and ChatGPT use browser OAuth and do not need a consumer key. Header-based clients use the endpoint and header above. |
| 35 | |
| 36 | Client configuration changes over time. Before giving client-specific steps, fetch the current source of truth: |
| 37 | |
| 38 | ```text |
| 39 | https://docs.composio.dev/docs/composio-connect.md |
| 40 | ``` |
| 41 | |
| 42 | Keep current documentation and CLI or tool schemas as the primary sources. If they do not answer a For You support question, query `https://docs.composio.dev/api/knowledge-search?q=<question>`. Results may be canonical docs, KB, toolkit, example, or reference pages. Use the returned evidence; do not infer the live state of a user's account, connection, or tool call from public records. |
| 43 | |
| 44 | For any other MCP-capable client, configure HTTP transport with the endpoint and, when required, the `x-consumer-api-key` header. Keep credentials out of committed configuration. |
| 45 | |
| 46 | ### Terminal agents |
| 47 | |
| 48 | Install and authenticate the CLI only when the task needs it: |
| 49 | |
| 50 | ```bash |
| 51 | curl -fsSL https://composio.dev/install | bash |
| 52 | composio login |
| 53 | ``` |
| 54 | |
| 55 | For a real task: |
| 56 | |
| 57 | ```bash |
| 58 | composio search "<what the user wants>" |
| 59 | composio link <toolkit> |
| 60 | composio execute <TOOL_SLUG> -d '{...}' |
| 61 | ``` |
| 62 | |
| 63 | `composio search` can return two toolkits for one product, such as `notion` and `notion_mcp`, and they are separate toolkits with separate connections. `composio link` links exactly the slug you give it, so link the same slug you plan to execute. |
| 64 | |
| 65 | Use `composio login --no-wait | jq` when the agent cannot open a browser. Give the returned login URL to the user and complete authentication with the returned key. Once installed, prefer the bundled `composio-cli` skill for current command and flag details. |
| 66 | |
| 67 | ## Connect apps when the task needs them |
| 68 | |
| 69 | Do not pre-connect every app. Start the requested task. When an integration is required, Composio returns an authorization link and the connection persists for future runs. |
| 70 | |
| 71 | For setup or an operational request, verify the selected path with one safe real call when authorization is available. For a question or configuration explanation, answer it without forcing execution. |
| 72 | |
| 73 | ## Debugging |
| 74 | |
| 75 | First confirm that the client is connected to the correct MCP endpoint or that the CLI is authenticated. Then get the Composio log or request ID and read [Errors and provider gotchas](errors.md). |
| 76 | |
| 77 | Common product-specific checks: |
| 78 | |
| 79 | - If MCP tools do not appear, confirm the connector is enabled, clear its cache when the client supports that, and reconnect it. |
| 80 | - If browser OAuth repeatedly selects the wrong account, retry in a clean browser profile with one Composio account signed in. |
| 81 | - If an authorization link expired, request a new link rather than reusing it. |
| 82 | - If a connected app action returns an auth error, reconnect that app and retry without regenerating the consumer key. |
| 83 | |
| 84 | Manage connections in Dashboard → For You → Connect Apps. Manage consumer keys and MCP or CLI sessions in Settings → Sessions & API Key. |