Support Storing Toolset Files Directly Within the Workspace

[jeffreyschultz]

I would like to request support for storing <name>.toolsets.jsonc files directly within the workspace. This enhancement would enable projects to be fully workspace-configurable, covering scenarios such as:

• Running MCP servers as part of the project setup
• Configuring Visual Studio Code to work with workspace-specific MCP servers
• Providing guidance for VS Code about how to interact with these MCP servers

Storing these configuration files in the workspace brings several benefits:

• Version Control: The configuration can be tracked and versioned with the rest of the project code.
• Team Consistency: All team members can share the same toolset definitions, ensuring a consistent development environment.
• Portability: Project setup becomes easier for new contributors, as all required configuration is included in the repository.

This feature would greatly improve collaboration and reproducibility for teams using MCP servers and workspace-specific toolsets.

[roblourens]

We should have this, but I'd like to hear more about what you're using toolsets for 🙂

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[corzo994]

+1 to this request

[ethanresnick]

Yes please!