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: explain App grouping and Composio Built vs Provider MCP toolkits (#5409)
## Summary Document App grouping and the choice between Composio Built and Provider MCP catalog toolkits. Each toolkit retains its own tools, authentication, and connections. Replaces the unmerged #4336 on current `next`. ## Changes - Add three Apps and toolkits guides, Platform sidebar navigation, and a toolkit-selection example in Python, TypeScript, and API form. - Add catalog terminology to the glossary, toolkit guidance for agents, and the Composio skill. - Explain backend-owned grouping, factual type labels, independent connections, and selection by tools, triggers, and authentication. Avoid suffix-based grouping and default recommendations. - Omit the outdated September staging screenshots. MCP gateway is a separate product. This PR leaves session configuration, session MCP, Composio Connect, MCP migration, Custom MCP setup, session guardrails, and the Markdown renderer unchanged. Existing Native Tools and MCP terminology in those docs and glossary definitions stays intact. The grouping contract was checked against the current dashboard `toolkit-provider.ts`: backend `app` groups catalog entries, missing values and custom toolkits stay singletons, and `toolkit_type` determines the type label. ## Type of change - [x] Documentation ## How has this been tested? After narrowing the scope, from `docs/`: - `bun run lint:links`: no errors. - `bun run check:code-examples` and `bun run check:api-snippets`: no violations across 453 files. - `bun test tests/static/product-navigation.test.ts tests/static/source.test.ts tests/static/session-execution.test.ts`: 18 pass, 0 fail. - `GITHUB_ACTIONS=true bun run build`: passed, including TypeScript and MDX checks. - Confirmed the eight session/gateway files listed above match the PR base byte for byte. The earlier broader revision also passed all 835 static tests, lint, and type checking. Browser inspection covered the new guides, sidebar, comparison table, API tab, and three working Markdown endpoints. ## Additional context The semantic-search artifact needs refreshing after the content changes. The existing CI check allows stale artifacts, and search falls back to keyword results until the semantic-artifact workflow rebuilds it. No embedding credentials or generated catalog data changed. No changeset is needed. No provider calls, authentication flows, merge, or production deployment were performed.
No changes.