Type

Enhancement

Problem / Value

Roo currently supports Global and Project MCP server settings and manages its own configuration. VS Code 1.102 stabilized MCP, and many users already have MCP servers (including GitHub Copilot Agent) configured there. Adding a “VSCode” scope lets users reuse those servers in Roo without duplicate setup, reducing friction and improving consistency.

Context

Affects users who use VS Code’s MCP ecosystem or GitHub Copilot Agent and want to use the same servers in Roo. This comes up when starting new projects or switching workspaces and they want their existing MCP setup to “just work” in Roo.

Desired Behavior

• Introduce a third MCP scope: “VSCode”, alongside existing Global and Project scopes.
• VSCode scope is auto-discovered and read-only: Roo lists VS Code’s MCP servers (including GitHub Copilot Agent) without editing them.
• Precedence: Project > VSCode > Global when the same server name exists.
• Users can enable/disable usage of each VSCode-sourced server within Roo.

Constraints/Preferences

• Do not modify VS Code’s MCP settings files (read-only in Roo).
• Clearly indicate scope (Global / Project / VSCode) in Roo’s UI.
• Keep behavior lightweight: no manual sync; discovery should be automatic.