Tools and Connections
Managing Toolkits
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:
Argument | Description |
---|---|
--kind / -k | The type of toolkit to import. Only mcp is supported at this time. |
--name / -n | The name of the toolkit. |
--description | The description for the toolkit. |
--package-root / -p | The root directory of the MCP server package. |
--command | The 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 / -t | A comma-separated list of tools to import, or * to import all available tools (e.g. --tools="tool_1,tool_2" ). |
--app-id / -a | The 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]
Import all tools using *
:
[BASH]
Command as string instead of JSON-style list:
[BASH]
Manually specify a list of tools:
[BASH]
Let the system fetch tools from the MCP server automatically:
[BASH]
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]