[FEATURE] Allow Claude Code VS Code extension to read MCP servers from VS Code's mcp.json

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Problem

When running Claude Code as a VS Code extension, MCP servers must be configured in two separate places:

1. VS Code's mcp.json (%APPDATA%\Code\User\mcp.json) — used by VS Code and other MCP-compatible tools
2. Claude Code's ~/.claude/settings.json under mcpServers — used exclusively by Claude Code

This creates maintenance burden and drift risk. When a server config changes (e.g., switching AWS profiles, regions, or ports), both files must be updated manually.

Proposed Solution

When Claude Code is running as a VS Code extension, it should be able to read MCP server configurations from VS Code's mcp.json. Possible approaches:

• Auto-discover: Automatically use servers defined in VS Code's mcp.json
• Opt-in setting: Add a setting like "useVSCodeMcpServers": true in ~/.claude/settings.json
• File reference: Support a "mcpConfigFile" field pointing to an external config file

Why This Matters

• Single source of truth for MCP server configuration
• No manual sync needed when configs change
• Consistent server availability across all VS Code MCP-compatible tools

Environment

• OS: Windows 11
• Claude Code: VS Code extension

Proposed Solution

When Claude Code is running as a VS Code extension, it should automatically detect and use MCP servers already configured in VS Code's mcp.json (%APPDATA%\Code\User\mcp.json) — without requiring the user to duplicate those entries in ~/.claude/settings.json.

Ideal experience:

1. I configure an MCP server once in VS Code's mcp.json (as I do today for other VS Code tools).
2. Claude Code, running as a VS Code extension, picks it up automatically — no extra config needed.
3. If a conflict exists between VS Code's mcp.json and Claude Code's own mcpServers config, Claude Code's config takes precedence.

An opt-in setting like "useVSCodeMcpServers": true in ~/.claude/settings.json would also be acceptable if auto-discovery is too implicit.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

MCP server integration

Use Case Example

_No response_

Additional Context

_No response_