Conversation
There was a problem hiding this comment.
I could probably give this file a bit more love but this should be good enough for a first iteration of tool filtering
|
Something I haven't discussed with anyone but want to do is: EDIT1: We might need another approach if we want to show just the enabled tools count in the servers tab table or the count in the Tools tab when viewing a server |
|
Hey @cmrigney, I didn't have time to look at Daniel's PR. Could you? Thanks! |
cmrigney
left a comment
There was a problem hiding this comment.
Nice addition! lgtm, just left a couple optional suggestions.
Tools filtering
What I did
Tool filtering
Add new commands:
docker mcp tools enable <toolName>anddocker mcp tools disable <toolName>. They auto-discover the first matching server using the catalog. Also they accept a--serverflag. It helps with duplicate tool names where the auto-discover might fail to find the server the user wants.The enabled tools are stored in a
tools.yamlfile which contains all the enabled tools grouped by server. Example file:read as:
The gateway reads and respects this file. When launching the gateway, the existing
--toolsoption (which accepts the tools names) takes precedence over thetools.yamlfile. This works the same way as the--serversoption and theregistry.yaml.Nice to haves:
tools.yamlif all of the server's tools are enabled--serverflagRelated issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did