Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 03:37 UTC
| 1 | # Apps and toolkits |
| 2 | |
| 3 | ## Decision |
| 4 | |
| 5 | Use **Composio Built** for toolkits Composio maintains against product APIs, **Provider MCP** for catalog toolkits backed by a product's hosted MCP server, and **Custom MCP** for remote servers registered for a project or one user. |
| 6 | |
| 7 | An **App** groups related catalog toolkits for comparison. Each toolkit retains its own slug, tools, authentication methods, auth configs, and connected accounts. App grouping does not enable sibling toolkits in a session or transfer a connection between them. |
| 8 | |
| 9 | ## Grouping and selection |
| 10 | |
| 11 | - The dashboard groups by the backend-owned `app` value. Missing values and Custom MCP toolkits remain singletons. |
| 12 | - Use `toolkit_type` to distinguish Composio Built from Provider MCP in dashboard code. Do not infer type or grouping from `_mcp`, `_graph`, or `_graphql` suffixes. |
| 13 | - A shared provider does not establish that toolkits serve the same job. Different products, acting identities, or deployment targets can remain separate. |
| 14 | - Do not recommend the first toolkit in a group. Honor an explicitly named slug; otherwise compare required tools, triggers, authentication, and existing connections. |
| 15 | - Composio managed auth availability is independent of toolkit type. |
| 16 | |
| 17 | ## Documentation scope |
| 18 | |
| 19 | The three guides cover App grouping, Provider MCP behavior, and choosing a toolkit. The glossary, toolkit guidance for agents, and the Composio skill use the same catalog terminology. MCP gateway is a separate product. Session and gateway docs, their Native Tools terminology, and their Markdown rendering remain unchanged. |
| 20 | |
| 21 | The replacement for PR #4336 carries the content onto the current `next` branch. It adds toolkit guidance to the current `docs/agent/instructions/context.ts`. |
| 22 | |
| 23 | The September staging screenshots are omitted because they contain personal workspace details, old counts, and grouping examples that no longer match the backend-owned contract. Fresh demo-workspace screenshots can be added separately. |
| 24 | |
| 25 | ## Verification boundary |
| 26 | |
| 27 | Review against the current docs and SDK contracts and the dashboard grouping implementation. Build, link, snippet, lint, and test results belong in the PR description. A local check does not establish production rollout or provider availability, and old test results from PR #4336 do not validate this replacement. |