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 | NPM or Python package of the MCP server. Runs a npx -y {packagename} or python -m {packagename} command automatically from the package structure. You must provide a --language flag with a value of either node or python to specify what language it uses. |
--package-root | The root directory of the MCP server package. |
--language | Tha language your package is based on. |
--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. |
*
:Delete the existing toolkit
Import the toolkit with the new specs
Import all agents that use the toolkit