SDK releases: custom toolkits in Python 0.31.0 and TypeScript 0.28.0
You can now create custom MCP toolkits for a single user or share them across your project. Both SDKs use Composio client2.0.1.
Release versions
All 13 Python provider packages are released at
0.31.0.
What’s new
- Custom MCP toolkits. Use
composio.experimental.custom_toolkits.create()in Python orcomposio.experimental.customToolkits.create()in TypeScript. Setuser_idoruserIdto a user ID for a private toolkit, or to'all'to share it across the project. Creation returns a generated slug and, when available, a connect link for a private toolkit. Store the slug and pass it toupdate()to change the name, logo, or API key input copy. TypeScript also acceptsadditionalFields.genericIdfor headers that use{{generic_id}}. - Trigger delivery and polling. Pass
typeto choose webhook or polling delivery for a trigger that supports both. Setpolling_intervalin Python orpollingIntervalin TypeScript to choose the minutes between polls. Created and listed instances include their delivery type, polling interval, and fallback reason. Trigger type metadata reports supported delivery types and whether webhook endpoint setup is required. - Session policies. TypeScript
sessionConfigs.get()preservesrequire_approvallists and accepts policy entries that contain only approval requirements. Toolkit metadata also exposesmeta.appUrlwhen the API returns it. - Anthropic compatibility. The TypeScript Anthropic provider accepts
@anthropic-ai/sdk^0.135.0.
Migration notes
- Custom toolkit registration.
upsert()still works, but warns once per process that it is deprecated. Before: register a toolkit with a caller-chosen slug throughupsert(). After: callcreate(), store its returned slug, and useupdate(slug, ...)for later metadata changes. The server URL, auth schemes, and owning user cannot change after creation; delete and create the toolkit again to change them. - Write retries. POST and PATCH requests are sent once by default. A write may complete on the server even when its response is lost, so retry only when you can prevent duplicate side effects. Reads keep their retry behavior. On the TypeScript client returned by
getClient(), opt a write into retries with that call’smaxRetriesoption. - Direct TypeScript client calls. Replace
client.request(...)withclient.get(path, options)for GET requests, retaining the relevant query and request options. For other HTTP methods, usepost,patch,put, ordelete. Resource classes,Composio.Tools-style statics, namespace-member types,Composio.Composio, andComposio.DEFAULT_TIMEOUTare removed. Import types from@composio/client/resources/*without.jsor.mjssuffixes, and use indexed access for nested types. - Session config search. TypeScript
sessionConfigs.list()ignores the deprecatedsearchoption and warns when you set it. Filter the returneditemsby name instead.
Bug fixes
- Local upload MIME types. Files uploaded from local paths use the MIME type of their extension instead of always using
application/octet-stream. Python and TypeScript use the same extension table. Files supplied asFileobjects or URLs keep the MIME type they carry. - Python downloaded filenames. Files downloaded from extensionless URLs use the extension corresponding to a known response MIME type, including formats such as CSV and PowerPoint. Unknown MIME types leave the generated filename extensionless.
- Python schema defaults. Default coercion handles schemas whose
typeis a list, including nullable types. - Python Gemini execution. Manual function-call handling uses the user or session you supply, and rejects ambiguous ownership instead of choosing the last user to fetch tools. See the Gemini provider fix.
- TypeScript session authorization. Sessions returned by
create()anduse()accept the already-supportedexperimentalauthorization options in their public types.