Integrate MCP `roots` and dynamic tool discovery

[digitarald]

It would be really great if repomix could leverage MCP features to create a more context-aware and adaptive experience. VS Code supports both of them and hopefully other MCP clients follow up as this can provide a much smoother tooling experience.

• MCP Roots Support: https://modelcontextprotocol.io/docs/concepts/roots#why-use-roots%3F

  • Allow repomix to accept multiple roots (like local paths or URLs) so it can automatically determine which part of a workspace or repository to pack.
  • Automatically configure tool parameters based on the current VS Code workspace.

• Dynamic Tool Discovery: https://modelcontextprotocol.io/docs/concepts/tools#tool-discovery-and-updates

  • Listen for list-change events to update available repo packs and tool definitions in real time.
  • Re-scan the workspace when changes are detected, ensuring operations always match the current project state.

Looking forward to your thoughts and suggestions on how to best implement these ideas!

[yamadashy]

Hi, @digitarald !

Thank you for sharing this information and your proposal!

I agree that MCP roots seems particularly promising from a security perspective as well.
While the tool discovery implementation details still need more work to define concrete specifications, I'll review and consider both suggestions on my end.​​​​​​​​