Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.watson-orchestrate.ibm.com/llms.txt

Use this file to discover all available pages before exploring further.

Manage the toolkits in your active environment.

​
Listing toolkits

Use the orchestrate tools list command to list all tools in your environment. You can also use the --verbose (-v) flag to get detailed information about each tool in JSON format.
BASH
orchestrate toolkits list -v
Exporting remote MCP toolkits with the ADK CLI enables you to package and distribute custom tool integrations for watsonx Orchestrate. This process ensures consistent agent workflows across environments and simplifies deployment for development, testing, or production. Use this capability when you need to share toolkits with other teams, migrate configurations, or maintain version control for your MCP integrations.

​
Exporting remote MCP toolkits using ADK CLI

Use the ADK CLI to export a remote MCP toolkit configuration for deployment or integration.
BASH
orchestrate toolkits export -n my-toolkit -o my-toolkit.zip

​
Updating toolkits

You can update Python toolkits and MCP toolkits in watsonx Orchestrate, but each type follows a different process.

​
Updating Python toolkits

You can update a Python toolkit by importing it again with your updated specifications. When you import the toolkit, watsonx Orchestrate replaces the existing version so you can continue working with the latest changes.
BASH
orchestrate toolkits add \
  --kind python \
  --name my-toolkit-name \
  --description "helps you talk to the manager" \
  --language python \
  --package <python-package-name> \
  --package_root <path-to-package-root> \
  --tier small

​
Updating local and remote MCP toolkits

Unlike python toolkits, it is not possible to update a MCP toolkit. Instead, the mcp toolkit must first be removed, and then reimported again as shown in the following example.
1

Delete the existing toolkit

BASH
orchestrate toolkits remove -n my-toolkit-name
2

Import the toolkit with the new specs

BASH
  orchestrate toolkits add \
      --kind mcp \
      --name my-toolkit-name \
      --description "helps you talk to the manager" \
      --package_root /path/to/folder \
      --command '["node", "dist/index.js", "--transport", "stdio"]' \
      --tools "*" \
      --app-id "my_app_id"
3

Import all agents that use the toolkit

For more information, see Importing agents.

​
Removing toolkits

Removing a toolkit will remove all tools provided by that toolkit. To remove an existing toolkit, run:
BASH
orchestrate toolkits remove -n my-toolkit-name