[BUG] Synced plugin MCP server hides a connected claude.ai connector with the same URL (no way to choose route)

Summary

When a plugin synced from claude.ai declares an MCP server with the same URL as one of my personal claude.ai connectors, Claude Code keeps the plugin's direct connection and hides the connector. If the service rejects direct connections, the CLI shows a misleading auth error, even though the same connector works in Claude Desktop. There is also no setting to choose which route a given server uses.

Environment

• Claude Code 2.1.287, Windows 11
• Personal account (connectors are not org-managed)

Steps to reproduce

1. On claude.ai / Claude Desktop, connect the Adobe connector (https://adobe-creativity.adobe.io/mcp). It shows as connected.
2. In Claude Desktop, install the adobe-for-creativity plugin. It syncs to the CLI as adobe-for-creativity@synced, and its .mcp.json points at the same URL.
3. Run claude mcp list in the CLI.

Actual

• Only plugin:adobe-for-creativity:Adobe for creativity is listed, with status Needs authentication. claude.ai Adobe is missing.
• Completing OAuth in the CLI gives: Got new credentials, but plugin:adobe-for-creativity:Adobe for creativity rejected them on reconnect.
• Root cause: the Adobe endpoint returns a bare 403 to any direct request, with or without a token, so the direct route can never work.
• The same thing happened with the synced github plugin. Its .mcp.json requires Bearer ${GITHUB_PERSONAL_ACCESS_TOKEN}; with the variable unset it fails with HTTP 400: Authorization header is badly formatted, while my claude.ai github connector was connected but hidden.

Expected

The CLI uses the claude.ai Adobe connector, which is already connected and works in Desktop.

Workaround: disabling the plugin with "adobe-for-creativity@synced": false in enabledPlugins makes claude.ai Adobe ✔ Connected appear immediately.

Suggestions

1. For plugins synced from claude.ai, prefer the matching claude.ai connector, the same way plugin servers already yield to org-managed connectors.
2. Add a setting to choose the route per server (for example "prefer claude.ai connector" vs "direct").
3. When a plugin server hides a connected claude.ai connector, say so in /mcp and /plugin, and in the auth error message.