Feature Request: Support disabling user-scoped MCP servers by default

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

Currently, disabledMcpjsonServers in settings.json only works for project-scoped
MCP servers (.mcp.json files). User-scoped MCP servers configured via
--scope user (stored in ~/.claude.json) cannot be disabled by default —
they are always active in every session.

The /mcp toggle is per-session only and resets on every new window.

Proposed Solution

A setting (e.g., disabledMcpServers) that works for ALL scopes including
user scope, allowing servers to be configured but disabled by default,
and temporarily enabled per-session via /mcp.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

Tools like playwright or playwright-cdp are useful occasionally across multiple projects, but having them always active wastes resources and
clutters
the MCP list. Users want to:

1. Keep them configured globally (user scope)
2. Have them disabled by default
3. Enable them temporarily when needed via /mcp

Additional Context

None that fully satisfies the requirement. Users must either:

• Manually claude mcp add/remove each time
• Use project scope (loses global availability)
• Accept that user-scoped servers are always enabled