Manage the toolkits in your active environment.

Important:

  • Currently, this feature is only available in the watsonx Orchestrate Developer Edition.
  • Currently, only node based MCP server is supported.

​
Importing toolkit

Use the orchestrate toolkits import command to import a toolkit into your environment. The following arguments are available:

ArgumentDescription
--kind / -kThe type of toolkit to import. Only mcp is supported at this time.
--name / -nThe name of the toolkit.
--descriptionThe description for the toolkit.
--package-root / -pThe root directory of the MCP server package.
--commandThe command used to start the MCP server. This can be a string (e.g. 'node dist/index.js --transport stdio') or a JSON-style list (e.g. '["node", "dist/index.js", "--transport", "stdio"]').
--tools / -tA comma-separated list of tools to import, or * to import all available tools (e.g. --tools="tool_1,tool_2").
--app-id / -aThe app ID to associate with this toolkit. Only key_value connections are supported.
Note: Use environment variables to expose the keys and values of the key_value connection to the MCP server.

Examples:

Import all tools using *:

[BASH]
orchestrate toolkits import \
    --kind mcp \
    --name 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"

​
Updating toolkit

To update an existing toolkit, run the orchestrate toolkits import command again using the same toolkit name. This re-imports the toolkit and applies any changes to its configuration.

​
Removing toolkit

To remove an existing toolkit, run:

[BASH]
orchestrate toolkit remove --n my-toolkit-name