[BUG] Strava connector appears under two different MCP server names across sessions, breaking permission rules

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:

The Strava connector (set up via the desktop app's Connectors UI) appears under different MCP server name prefixes depending on session context, making it impossible to write a stable permission rule that covers both.

Observed behavior:

In some sessions the tools appear as:

mcp__claude_ai_Strava__list_activities
mcp__claude_ai_Strava__get_activity_performance
... etc
In other sessions (including after reconnection) the same connector appears as:

mcp__c72258c0-3335-4694-b1c6-fd7b068c2709__list_activities
mcp__c72258c0-3335-4694-b1c6-fd7b068c2709__get_activity_performance
... etc
The switch appeared to correlate with running claude auth login — the friendly name appeared afterward, then reverted to the UUID on reconnect.

Impact:

Permission rules in ~/.claude/settings.json (e.g. mcp__claude_ai_Strava__*) only work in sessions where that name is used. The other form still prompts. Workaround is to add both forms, which is fragile since the UUID could change again.

Expected behavior:

A connector set up via the UI should have a single stable, human-readable server name across all sessions and auth states.

Environment:

macOS
Claude Code desktop app + CLI

What Should Happen?

Stay the same

Error Messages/Logs

None

Steps to Reproduce

N/A

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.153 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_