Desktop app doesn't surface MCP prompts as /mcp__server__prompt slash commands (works in terminal CLI)
What happened
An MCP server connected over HTTP exposes an MCP prompt (e.g. space_health). In the terminal CLI, this correctly appears as a slash command /mcp__<server>__<prompt> and is invokable. In the Claude Code desktop app, the same MCP prompt does not appear in the / menu, even though the same MCP server is connected and its tools work in both surfaces.
So on desktop: MCP tools ✅, MCP prompts ❌ (not surfaced as slash commands).
Expected
MCP prompts should surface as /mcp__<server>__<prompt> slash commands in the desktop app, matching the terminal CLI behavior documented at https://code.claude.com/docs/en/mcp#use-mcp-prompts-as-commands.
Notes
The docs don't currently state whether this is intentional. The desktop / menu docs list built-in commands, custom skills, and plugin skills, but never mention MCP prompts; MCP tools and resources are documented as working in desktop. This reads as either a missing feature or a docs gap.
Either way, a request:
- If unsupported: please add MCP-prompt slash-command support to the desktop app for parity with the CLI.
- If it's a known limitation: please document it in the desktop feature-comparison section so it's discoverable.
Environment
- Claude Code desktop app (macOS) vs Claude Code terminal CLI
- MCP server: remote HTTP transport, OAuth-gated, exposes tools + prompts