Prerequisites
What are you trying to do that currently feels hard or impossible?
We manage our tools.yaml configuration and the mcp-toolbox deployment across two separate services. Because these services have independent release cadences, keeping them perfectly synchronized during deployments is nearly impossible.
As a result, when upgrading mcp-toolbox, any tools currently defined in tools.yaml that have been deprecated or removed in the newer toolbox version (such as the removal of looker-git-branch in v1.0.0) cause startup failures.
Suggested Solution(s)
Add command line flag --ignore-unknown-tools that prints warning in logs but allow to run the toolbox. This will also ensure that unknown tools will be skipped and will not be present in tools/list
Alternatives Considered
No response
Additional Details
No response
Prerequisites
What are you trying to do that currently feels hard or impossible?
We manage our tools.yaml configuration and the mcp-toolbox deployment across two separate services. Because these services have independent release cadences, keeping them perfectly synchronized during deployments is nearly impossible.
As a result, when upgrading mcp-toolbox, any tools currently defined in tools.yaml that have been deprecated or removed in the newer toolbox version (such as the removal of looker-git-branch in v1.0.0) cause startup failures.
Suggested Solution(s)
Add command line flag --ignore-unknown-tools that prints warning in logs but allow to run the toolbox. This will also ensure that unknown tools will be skipped and will not be present in tools/list
Alternatives Considered
No response
Additional Details
No response