[BUG] Disconnected cloud MCP connectors (e.g. Atlassian) still trigger browser OAuth prompt on every session start

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Description:
Cloud MCP connectors that are listed under "Not connected" in Claude.ai Settings → Connectors still spawn mcp-remote processes and trigger browser OAuth prompts on every Claude Code session start. Specifically, Atlassian Rovo opens a browser tab requesting MCP CLI Proxy access on each new session, even when:

The connector is not connected in Claude.ai (Settings → Customize → Connectors)
The local Atlassian plugin is disabled (enabledPlugins set to false in ~/.claude/settings.json)
The Atlassian entry has been removed from ~/.claude/mcp_server_config.json
The ~/.claude/mcp-needs-auth-cache.json has been cleared (it repopulates with "claude.ai Atlassian" on every session start)
The connector has been fully removed from the Claude.ai connectors list

What Should Happen?

I should not continually get prompted to authenticate this MCP when I have disabled it on my Claude account and even removed it from my organization.

Error Messages/Logs

Steps to Reproduce

1. Have a Claude Max account with the Atlassian connector previously connected then disconnected
2. Confirm Atlassian shows under "Not connected" in Claude.ai → Settings → Customize → Connectors (or is removed entirely)
3. Open a new Claude Code session (VSCode extension)
4. Browser opens to Atlassian Rovo OAuth page: "MCP CLI Proxy is requesting access"

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

This worked this morning, and does not work now.

Claude Code Version

Claude Code 2.1.42.

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_