Dynamic Tool Discovery

[pulkitsharma07]

Currently the mcp server exposes all tools by default. As we add support for more tools, this will lead to increased token usage and can also cause confusion/hallucinations in tool usage by the MCP clients.

Github has implemented dynamic toolsets to address this: github/github-mcp-server#275

For TypeScript we can use this feature: https://github.com/modelcontextprotocol/typescript-sdk?tab=readme-ov-file#dynamic-servers

Instead of toolsets/launch args or flags while installing the MCP server, We can expose one tool initially: enableProducts which will take a list of products to enable tools for, i.e. ["automate", "test management", ...] and then enable only those tools.

[aryan4codes]

Hey @pulkitsharma07 ,
I’ve just opened a PR to address issue #64 — looking forward to your feedback! Please let me know if there’s anything I can improve or tweak. I’m interested in contributing more, especially around MCPs, so any suggestions are welcome.

Also, if possible, feel free to post more issues — I’d be glad to take them up and help out wherever I can.

Thanks!

[pulkitsharma07]

Thanks for the contribution @aryan4codes we will get back on this. @ruturaj-browserstack please check.