I can't speak to anything but Claude but this works in Claude Code CLI.  It does not work in Claude Desktop.  When asking Claude desktop for an explanation I get the following:   The core difference comes down to how MCP tool results are surfaced in each environment: Claude Code CLI runs in a terminal context where MCP tool responses come back as raw structured data (JSON, text, etc.) directly in my context window. I can read every field, every value — the full payload. Claude in the web interface (me, right now) integrates MCP servers differently. The tool results appear to be getting summarized or only partially surfaced — I can see metadata like "Tool executed successfully (1 result)" but the actual row data and field values aren't being passed through to me in a readable way. I know that a query ran and how many rows came back, but I can't read what's in those rows. It's essentially a display/integration layer issue specific to how the claude.ai web UI handles MCP tool responses compared to Claude Code's terminal-native integration, which gives full fidelity access to the raw output. So it's not a capability gap on my end — it's an artifact of how MCP results are being piped into my context in this particular interface. If you're doing heavy Splunk work via MCP, Claude Code CLI is genuinely the better tool for that workflow right now. You could also feed me query results directly by pasting them into the chat, and I can analyze them just fine that way. Although it refers to itself as running in the web interface, I'm assuming that's just because claude desktop is a wrapped web app.   ... View more