MCP servers with "disabled": true in mcp-config.json are still loaded and available

[mstehrani]

Describe the bug

MCP servers marked with "disabled": true in ~/.copilot/mcp-config.json are still being loaded and their tools are available in the session. The disabled flag is completely ignored by the CLI runtime.

Affected version

1.0.57-0

Steps to reproduce the behavior

1. Open ~/.copilot/mcp-config.json
2. Set "disabled"#COLON| true on one or more MCP server entries:
   {
   "mcpServers": {
   "calendar": {
   "disabled": true,
   "type": "sse",
   "url": "https://example.com/sse",
   "headers": { ... }
   }
   }
   }
3. Start a new Copilot CLI session
4. Observe that tools from the "disabled" servers are still listed and callable

Expected behavior

Servers with "disabled": true should not be connected, and their tools should not be available in the session.

But in actuality, all MCP servers are loaded regardless of the disabled flag. In my case, 8 servers are marked disabled: true and all 8 have their tools available

Additional context

• Copilot CLI version: 1.0.57-0
• OS: Windows 11
• Config file: ~/.copilot/mcp-config.json
• Model: Claude Opus 4.6