`/mcp` in a Remote Control session shows account connectors instead of the session's MCP servers

Environment: Claude Code 2.1.280, macOS, server started with claude rc (spawn mode, same-dir). Session opened from the Claude mobile app / desktop app.

Steps:

1. Configure local stdio MCP servers in ~/.claude.json (e.g. mcp-grafana, npx slack-mcp-server, npx @playwright/mcp).
2. Start claude rc from a login shell.
3. Open a new session from the mobile/desktop app and run /mcp.

Expected: The per-session "MCP servers" dialog listing every server the session loaded, including the local Desktop-type ones, as happens for sessions the Desktop app runs itself.

Actual: It opens the account-level Connectors settings page. That page lists only claude.ai connectors, so none of the local servers appear. The servers are running and work: they're child processes of the session's claude --sdk-url process, and their tools are callable. The UI just makes it look like the session is missing them.

Impact: Users conclude Remote Control doesn't load local MCP servers and start debugging a problem that doesn't exist.