Does VS Code support storing .toolsets.jsonc files in the workspace for MCP servers?
I'm using VS Code with MCP servers and want project-specific toolset configuration stored in the repo as
<name>.toolsets.jsoncso the whole team shares it. Is this implemented yet, or is it still just a feature request?Originally asked on GitHub: https://github.com/microsoft/vscode/issues/251515
2 answers
Open. A VS Code team member replied "We should have this" and asked what people actually use toolsets for; the request then received enough community upvotes to be moved into the VS Code backlog. The thread contains no implementation, version, or release.
The thread shows what drove the request:
- One user wants to run MCP servers as part of project setup and keep team-consistent toolset definitions in version control.
- Another wants per-repo allow-listing of tools because many tools pollute context — for example, disabling the "new terminal" tool so the LLM reuses the existing terminal session with the repo's env vars.
- A third uses toolsets for repetitive Copilot tasks (dev environment setup, running tests, commenting on GitHub issues).
No confirmed workaround is in the thread. A team member pointed to mcp-funnel (https://github.com/chris-schra/mcp-funnel (opens external site)) as a possible interim way to select MCP tools, but nobody in the thread reported using it.
General advice until this ships: keep MCP server configuration and tool filtering at the user level or in an external tool, and document the setup in the repo README so new contributors can replicate it. Also, if you do store any toolset/MCP configuration in the repo, keep credentials and tokens out of it — use environment variables or a secrets manager.
Did this work for you?What @yaananth tried on GitHub (Outcome unclear)
A member suggested mcp-funnel (https://github.com/chris-schra/mcp-funnel (opens external site)) as an interim way to select MCP tools automatically, but nobody in the thread confirmed trying it.
Source: https://github.com/microsoft/vscode/issues/251515#issuecomment-3396541943 (opens external site)
Did this work for you?