Skip to main content
A toolkit is a collection of related tools for a single app, like gmail, github, or slack. Each toolkit groups the actions for that service, its authentication requirements, and the trigger types it exposes. Reach for these endpoints when you want to:
  • List the toolkits in the catalog, sorted by popularity, to browse what is available before configuring a session.
  • Fetch a single toolkit by slug for its name, logo, categories, and metadata.
  • Fetch several toolkits at once with the multi endpoint.
  • List the available toolkit categories to filter the catalog by use case.
  • Read the toolkits changelog to track when tools or schemas change.
These endpoints authenticate with your project API key in the x-api-key header.
Tools within a toolkit are versioned. When you execute a tool, resolve to a known version with toolkit_versions=latest or a pinned dated version. See the toolkit versioning migration guide.
To browse toolkits visually, see the toolkits catalog. For the concepts and SDK usage, see Tools and toolkits and Configuring sessions.

List available toolkits

Retrieves a comprehensive list of toolkits of their latest versions that are available to the authenticated project. Toolkits represent integration points with external services and applications, each containing a collection of tools and triggers. This endpoint supports filtering by category and management type, as well as different sorting options.

Get toolkit by slug

Retrieves comprehensive information about a specific toolkit using its unique slug identifier. This endpoint provides detailed metadata, authentication configuration options, and feature counts for the requested toolkit.

List toolkit categories

Retrieves a comprehensive list of all available toolkit categories from their latest versions. These categories can be used to filter toolkits by type or purpose when using the toolkit listing endpoint. Categories help organize toolkits into logical groups based on their functionality or industry focus.

Get toolkits changelog

Retrieves the last 10 versions changelog for all toolkits. This endpoint provides version history and changelog information for each toolkit.

List grant contexts

Experimental: this endpoint is in beta and its contract may change. List of contexts in which you want to grant scopes to your user. Pass a dimension and its selected value in the `grant_context` field of the [Get required scopes](/reference/api-reference/toolkits/recommendToolkitScopes) request to tailor the scope recommendation. In the Jira example, `default_grant_context` is `{"scope_family": "classic"}`, so a recommendation with no `grant_context` uses classic scopes. Pass `{"scope_family": "granular"}` to get granular scopes instead.

Create a custom toolkit

Experimental: this endpoint may change. Creates a custom MCP toolkit and returns its slug. Set user_id to "all" to share the toolkit with every user in the project, or to a user ID to make it private to that user ("default" and other spellings of "all" are rejected). Access cannot be changed later. For a private toolkit, the response can include a connect_link to send that user to.

Sync a custom toolkit

Experimental: custom toolkits are in pilot and this contract may change. Re-fetches tool definitions from the remote MCP server for the custom toolkit with the provided slug. Call it when automatic sync fails or the remote tool definitions change.

Upsert a custom toolkit

Experimental: custom toolkits are in pilot and this contract may change. Creates a custom toolkit for the project with the provided slug, or updates its display metadata (name, API key field copy) when the project already owns a toolkit with that slug. A toolkit created here is shared with every user in the project; an existing toolkit keeps its access. app_url and auth_schemes cannot be changed on an existing toolkit: re-sending them unchanged is a no-op, changing them returns 409 (delete and re-register the toolkit instead, which revokes its connections).

Fetch multiple toolkits

Retrieves a comprehensive list of toolkits of their latest versions that are available to the authenticated project. Toolkits represent integration points with external services and applications, each containing a collection of tools and triggers. This endpoint supports filtering by category and management type, as well as different sorting options. You can optionally specify a list of toolkit slugs to fetch specific toolkits.

Get required scopes

Experimental: this endpoint is in beta and its contract may change. Recommends the required scopes to use the given set of tools.

Update a custom toolkit

Experimental: this endpoint may change. Updates a custom toolkit's name, logo, or API key field text. Omitted fields keep their current value. To change app_url, auth_schemes, or user_id, delete and re-create the toolkit. On a project with 2FA enabled, updating a private toolkit requires the user_id it is private to.

Delete a custom toolkit

Experimental: custom toolkits are in pilot and this contract may change. Deletes a custom toolkit owned by the project, along with its tools, auth configs, and connected accounts, and revokes the upstream credentials of those connected accounts. Pass `?revoke_on_delete=false` to keep the credentials. Composio-managed toolkits cannot be deleted and return 403.