Data API Functions Fail with Claude Desktop

[CMduPreez]

Environment

OS: Windows 11
MCP Client: Claude Desktop (v0.12.55)
Server: google-analytics-mcp (latest from main branch)
Python: 3.13
Authentication: Application Default Credentials (ADC)

Issue Summary
Admin API functions work correctly, but all Data API functions return "No result received from client-side tool execution" when used with Claude Desktop as the MCP client.
Working Functions ✅

get_account_summaries - Returns complete account and property data
Other Admin API functions (assumed working based on account summaries success)

Failing Functions

run_report - Returns "No result received from client-side tool execution"
get_property_details - Returns "No result received from client-side tool execution"

Authentication Setup

# ADC configured with correct scopes
gcloud auth application-default login --scopes=https://www.googleapis.com/auth/analytics.readonly,https://www.googleapis.com/auth/cloud-platform

# Token verification shows correct scopes
curl "https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=TOKEN"
# Returns: "scope": "https://www.googleapis.com/auth/analytics.readonly https://www.googleapis.com/auth/cloud-platform"

Claude Desktop Configuration

{
  "mcpServers": {
    "analytics-mcp": {
      "command": "pipx",
      "args": [
        "run",
        "--spec",
        "git+https://github.com/googleanalytics/google-analytics-mcp.git",
        "google-analytics-mcp"
      ]
    }
  }
}

Reproduction Steps

1. Set up ADC with correct scopes using gcloud auth application-default login
2. Configure analytics-mcp server in Claude Desktop
3. Restart Claude Desktop
4. Call get_account_summaries - Works perfectly
5. Call run_report with valid parameters - Fails with "No result received from client-side tool execution"

Expected Behaviour
Data API functions should return report data just like Admin API functions return account data.

Actual Behaviour
Data API functions fail silently with "No result received from client-side tool execution" error.

Additional Context

• The server can be executed directly via pipx run --spec git+https://github.com/googleanalytics/google-analytics-mcp.git google-analytics-mcp without errors
• ADC credentials are valid and include the required scopes
• The same authentication previously worked with manual token configuration (using @accesstokenprototype branch)
• Admin API and Data API use the same authentication, but only Admin API functions work

Just figured its important you know this all

[jradcliff]

Hi,

The MCP server uses async methods, and although Gemini handles these without issue, I suspect that Claude doesn't. I'm looking into it.

Thanks,
Josh, Google Analytics team

[jradcliff]

We tested setting up the MCP server with Claude and Gemini, including on Windows, and here's what worked for us:

1. Set the GOOGLE_APPLICATION_CREDENTIALS env var to the full path to your credentials file in your Claude/Gemini settings, even if you're using Google Application Default Credentials (ADC). Claude and Gemini Code Assist don't seem to work properly with ADC.
2. Set the GOOGLE_PROJECT_ID env var in your Claude/Gemini settings.
3. If using Claude, completely shut down and restart Claude after updating settings. If you're on Windows, this will require quitting Claude from the sys tray.

Could you please give that a try and let us know how it goes?

Thanks,
Josh

[jradcliff]

A few more tips:

1. Make sure pipx is working properly. You can verify by running pipx run cowsay -t mooooo and confirm that prints some ASCII art to the terminal without any errors.
2. Use the simplified pipx arguments of ["run", "analytics-mcp"] in the command for the server in your Claude/Gemini settings.

[AdamGustavsson]

OpenAI Codex vsCode plugin does not "see" the run_report tool. The other tools work fine.
Perhaps some format issue in the tool description?
Related to the same issue?

[jradcliff]

@AdamGustavsson , does the OpenAI Codex vsCode plugin "see" the run_realtime_report and get_custom_dimensions_and_metrics tools?

Also, does your ~/.codex/config.toml file include both GOOGLE_APPLICATION_CREDENTIALS and PROJECT_ID in the env section?

Thanks

[AdamGustavsson]

yes it sees run_realtime_report and get_custom_dimensions_and_metrics tools.
I looked into the codex rust code and they only fetch the first page. Is the list/tools call paginated with 5 tools on each page?

[AdamGustavsson]

@jradcliff I also notice that Cursor also only show the first 5 in the UI (for enabling and disabling them) The cursor agent can use the last tool though.

[jradcliff]

Interesting, it does seem like their call to list tools doesn't paginate:

https://github.com/openai/codex/blob/bffdbec2c54eab4ff9c412ed8c4ae39c4566d28a/codex-rs/mcp-client/src/mcp_client.rs#L330

What happens if you issue a prompt that you'd expect to invoke the run_report tool? Does it find the tool in that case, or just say it can't handle the prompt?

[AdamGustavsson]

It tries to use the run_realtime_report instead and when asked to list all available tools it lists just the first 5.
Had it been some of the less used tool then I could live with it but without the run_report there is not much value. 😀
It really a problem on their end but I have not seen it before and I have used MCPs with codex that have more tools than five but I'm not sure if they use FastMCP.

[AdamGustavsson]

might be related to this too:
openai/codex#4176 (that would indicate that som validation fails)
When using /mcp it does list all tools but the agent is unaware of run_report

[AdamGustavsson]

Yes that was it:
2025-09-24T18:43:27.993287Z ERROR codex_core::openai_tools: Failed to convert "analytics-mcp__run_report" MCP tool to OpenAI tool: Error("invalid type: map, expected a boolean", line: 0, column: 0)
Not sure what it is that is a map but should be a boolean

[AdamGustavsson]

I think its this in the run_reprort input schema :

"date_ranges": {
  "type": "array",
  "items": {
    "type": "object",
-   "additionalProperties": { "type": "string" }
+   "additionalProperties": true //codex expects a boolean here
  }
}