[BUG] Desktop app: /mcp opens Connectors panel that omits project-scoped (.mcp.json) servers — no way to check their status

Environment: Claude Code desktop app, macOS (Darwin 25.5.0)

What happens: In a desktop-app session, typing /mcp opens the Connectors panel. That panel lists only account-level claude.ai connectors. MCP servers registered in the project's .mcp.json (project scope) do not appear — even when they are demonstrably connected and serving tools in the active session.

Expected: /mcp should show all MCP servers attached to the current session — including project-scoped servers from .mcp.json — with their connection status, as the CLI's /mcp dialog and claude mcp list do.

Impact: There is no UI affordance in the desktop app to verify whether a project-scoped server is active or failed. The only workarounds are asking the model to probe a tool, or running claude mcp list in a separate terminal.

Repro:

1. Project with .mcp.json registering any stdio server (e.g. Laravel Boost: vendor/bin/sail artisan boost:mcp).
2. Open the project in the desktop app; confirm the server's tools respond in-session.
3. Type /mcp → Connectors panel opens → the project server is absent.