Support Visual Studio .mcp.json schema (servers) to avoid cross-tool conflicts

When a user has both Claude Code and Visual Studio (with GitHub Copilot) configured, they share a ~/.mcp.json file. Visual Studio uses "servers" as the top-level key; Claude Code expects "mcpServers". Claude Code flags the file as a parse error on startup ("Does not adhere to MCP server configuration schema"), and there is no way to tell Claude Code to ignore the file.

Any workaround causes the equivalent problem in the other tool (e.g. adding "mcpServers" to the file produces a schema validation warning in Visual Studio).

Request: Either (1) add support for the Visual Studio "servers" key format in .mcp.json, or (2) provide a setting to exclude specific .mcp.json paths from parsing.