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
Apps and toolkits
Decision
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.
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.
Grouping and selection
- The dashboard groups by the backend-owned
appvalue. Missing values and Custom MCP toolkits remain singletons. - Use
toolkit_typeto distinguish Composio Built from Provider MCP in dashboard code. Do not infer type or grouping from_mcp,_graph, or_graphqlsuffixes. - A shared provider does not establish that toolkits serve the same job. Different products, acting identities, or deployment targets can remain separate.
- Do not recommend the first toolkit in a group. Honor an explicitly named slug; otherwise compare required tools, triggers, authentication, and existing connections.
- Composio managed auth availability is independent of toolkit type.
Documentation scope
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.
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.
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.
Verification boundary
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.