Can Roo Code use MCP servers registered in VS Code?
Roo-Code manages its own MCP servers at the Global and Project levels, but there is no built-in way to use the MCP servers registered in VS Code (for example, those used by GitHub Copilot). A feature request asking for a third "VSCode" MCP server type was filed in July 2025 against Roo-Code and closed as a duplicate. Is there a workaround to share VS Code MCP servers with Roo-Code?
Originally asked on GitHub: https://github.com/RooCodeInc/Roo-Code/issues/5619
4 answers
Not implemented as of this thread: the request was closed as a duplicate, and no merged or released version is mentioned in the discussion. A maintainer said the idea is solid and worth scoping, but that any VS Code MCP integration should keep all VS Code MCPs disabled by default so users' existing MCP configurations aren't unexpectedly added to Roo Code.
Workarounds from the thread:
- The proof-of-concept author built a separate VS Code extension, vs_code_lm_tools_mcp (github.com/craigsteyn/vs_code_lm_tools_mcp), that hosts all vscode.lm.tools as an MCP server on a configured port. The author asked Roo to build it and reported it "sorta seems to work" — the thread does not describe the exact port or connection details.
- A proof-of-concept patch on a personal fork (github.com/craigsteyn/Roo-Code/pull/1) exposes vscode.lm.tools and vscode.lm.invokeTool as a custom MCP server type named "vscode". The author called it hacky, said they were hitting issues, and noted it was unclear whether vscode.lm.tools returns all tools or only enabled ones.
For anyone implementing this, the thread references microsoft/vscode-copilot-chat as a starting point; the APIs identified include vscode.lm.selectChatModels, vscode.lm.tools, vscode.lm.invokeTool, vscode.lm.registerChatModelProvider, and vscode.commands for the MCP setup flow. A later comment (September 2025) says a potential fix is being explored with a PR to come; no merged code appears in this thread.
Security note (general advice): review which MCP servers VS Code has registered before letting another agent call them, since the maintainer's default-off position exists because this would share the VS Code/Copilot MCP setup.
Did this work for you?What @craigsteyn tried on GitHub (Outcome unclear)
A contributor patched their Roo-Code fork to expose vscode.lm.tools and vscode.lm.invokeTool as a custom MCP server type named "vscode" (personal fork PR). They called it hacky, said they were hitting issues, and were unsure whether vscode.lm.tools lists all tools or only enabled ones.
Source: https://github.com/RooCodeInc/Roo-Code/issues/5619#issuecomment-3129113560 (opens external site)
Did this work for you?What @craigsteyn tried on GitHub (Partly worked)
The same author had Roo build a separate VS Code extension (vs_code_lm_tools_mcp) that hosts all vscode.lm.tools as an MCP server on a configured port. The author reported it "sorta seems to work"; details of the port and connection setup were not given.
Source: https://github.com/RooCodeInc/Roo-Code/issues/5619#issuecomment-3129699013 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Another commenter said they were exploring a potential fix for the feature request and would open a PR to add support for VS Code MCP servers alongside Global and Project level configurations. No merged code is shown in this thread.
Source: https://github.com/RooCodeInc/Roo-Code/issues/5619#issuecomment-3269012747 (opens external site)
Did this work for you?