Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs(skills): clarify surface discovery
Kshitij Jhunjhunwala committed
Aug 10, 2026 at 14:36 UTC
ecd9b5ada801c21695610eed1473253f66e342b3
1 file changed
+14
skills/composio/references/for-you.md
+14
@@ -15,6 +15,20 @@ The removed `mcp.composio.dev` endpoint and Platform MCP URLs are not substitute
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.