Per-project opt-in toggle for user-scope MCP servers / claude.ai connectors (default off, remembered)

Feature request: per-project opt-in toggle for user-scope MCP servers and claude.ai connectors (default off everywhere, remembered when enabled)

Right now, any user-scope MCP server and every claude.ai connector (e.g. Gmail) is on by default in every project. The only way to turn one off somewhere is /mcp → disable, which writes an opt-out entry to disabledMcpServers in ~/.claude.json for that one project. This means every new project starts with all of them enabled, and I have to remember to manually disable the ones I don't want there — which doesn't scale as the number of projects and connected servers grows.

Requested behavior: the reverse default — a server/connector starts disabled in every project, and I explicitly enable it per project only where I actually need it. Once enabled in a project, Claude Code should remember that choice (persist it, the same way disabledMcpServers persists a disable) so I don't have to re-enable it every session.

Example: I have the Gmail claude.ai connector connected to my account, and a custom user-scope MCP server for a personal Telegram tool. I only need Gmail in one specific project (email drafting) and the Telegram server in one other project (a bot I'm building). Today both show up enabled in all ~80 of my projects, so I have to hunt down and /mcp disable them one project at a time. I'd like to instead flip a per-server default to "off," then just /mcp enable <server> in the one or two projects that need it, with Claude Code remembering that per project.

local-scope servers already behave close to this (they only exist in the project you add them to), but that only works for servers I add myself with that scope — it doesn't help with user-scope servers I want available in some projects, or with claude.ai connectors, which currently have no opt-in path at all.