@devries-cameron20 / composio-1 / commits / 26ec989e8
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

feat(sdk): expose custom toolkits outside the experimental namespace (PLEN-4879) (#5298)

<!-- claude-projects-attribution: {"github_login":"singhbharath03"} --> _Requested by **Bharath** · [project thread](https://claude.ai/code/project/chan_01Ceg3UUAuzX7NPb6jdX94JX?thread=cmsg_01Ceg3UUAuzX7NPb6jdX94JXT5EUqnomMb27iPoAEBNRpo)_ ## Summary Custom MCP toolkits are no longer experimental. The upcoming OAuth and CIMD changes are additive and non-breaking, and the experimental label is putting customers off using custom MCP. Today the SDK exposes them only at `composio.experimental.customToolkits` (TS) / `composio.experimental.custom_toolkits` (Python), so every code sample says "experimental". Linear: [PLEN-4879](https://linear.app/composio/issue/PLEN-4879/promote-sdk-custom-toolkits-out-of-the-experimental-namespace) (sub-ticket of [PLEN-4878](https://linear.app/composio/issue/PLEN-4878/remove-experimental-flags-from-custom-mcp-apis)). The API side is ComposioHQ/platform#14866. ## Changes - TS: new `composio.customToolkits`; `composio.experimental.customToolkits` is the same object, marked `@deprecated`. - Python: new `composio.custom_toolkits`; `composio.experimental.custom_toolkits` is the same object. The class is now `CustomToolkits`, and `ExperimentalCustomToolkits` stays exported as an alias. - Drops "Experimental, custom toolkits are in pilot" from the docstrings and points examples and the `upsert()` deprecation message at the new path. - Regenerated TypeScript SDK reference; changeset (minor) for `@composio/core`, `@composio/slim` and the Python SDK. - No runtime deprecation warning on the old path, so existing callers see no new output. ## Type of change - [ ] Bug fix - [x] New feature - [ ] Refactor/Chore - [x] Documentation - [ ] Breaking change ## How Has This Been Tested? - `ts/packages/core`: `vitest run` (78 files, 2017 passed), `tsc --noEmit` clean. New test asserts `composio.customToolkits` is a `CustomToolkits` and `composio.experimental.customToolkits` is the same object. - Python: `pytest tests/test_sdk.py tests/test_experimental_custom_toolkits.py` (54 passed). `test_sdk.py` now asserts `composio.custom_toolkits` and that the experimental path and class alias resolve to it. ## Checklist - [ ] I have read the Code of Conduct and this PR adheres to it - [ ] I have read and understand every line of this diff, including any LLM-generated code - [ ] Any third-party docs links or promotional content follow the third-party links policy - [x] I ran linters/tests locally and they passed - [x] I updated documentation as needed - [x] I added tests or explain why not applicable - [x] I added a changeset if this change affects published packages ## Additional context The Custom MCP guide (`docs/content/docs/extending-sessions/custom-mcp.mdx`) moves to the new path in a separate PR (PLEN-4880), after an SDK release contains this change. --- _Generated by [Claude Code](https://claude.ai/code/session_01H6YzWpsJUx7GVXrFfgStg6)_

Bharath Singh committed Nov 10, 2026 at 16:33 UTC 26ec989e86fd1195dfbdb780ba39668eb13e5b45

No changes.