Every client, and the config it actually wants
Most MCP installation guides give you one JSON block and tell you it works everywhere. It does not. Across the seventeen clients below there are six different root keys, four different names for the environment object, and four file formats.
Copying a Claude Desktop snippet into Hermes produces a file that parses and registers no servers. Copying one into OpenCode produces a server that never appears. Neither reports an error.
| What varies | Values across these clients |
|---|---|
| Root key | mcpServers (most clients), servers (VS Code), context_servers (Zed), mcp (OpenCode), mcp_servers (Hermes), mcp.servers (OpenClaw, ZCode) |
| Environment key | env (most), envs (Goose), environment (OpenCode), env plus env_vars (Codex) |
| Command shape | String everywhere except OpenCode, which takes an array |
| File format | JSON (most), TOML (Codex), YAML (Goose, Hermes, DeepSeek) |
Every block on the pages below is quoted from that vendor's own documentation, with the source page named. Where a vendor has not published a path, this site says so instead of inventing one.
| Client | What the page covers |
|---|---|
| Claude | Add the GA4 MCP server to Claude Code with one CLI command, or to Claude Desktop with one JSON entry. Includes five production natural language prompts. |
| Cursor | Add the GA4 MCP server to Cursor with a project or global mcp.json entry. Includes the type-field inconsistency Cursor's own docs carry. |
| VS Code | Add GA4 MCP to VS Code Copilot agent mode. Includes the critical root key distinction between .vscode/mcp.json and .mcp.json plus sample queries. |
| Codex | Add the GA4 MCP server to OpenAI Codex. Codex uses TOML, not JSON, and splits environment handling into env and env_vars — the two are not interchangeable. |
| Gemini CLI | Add the GA4 MCP server to Gemini CLI. The scope flag defaults to project, so the entry lands in .gemini/settings.json and not your home directory. |
| Antigravity | Add the GA4 MCP server to Antigravity, App, IDE or CLI. All three read the same mcp_config.json schema, and the App registers servers through the settings UI. |
| Zed | Add the GA4 MCP server to Zed. Zed calls them context servers, not mcpServers, and the entry lives in Zed's own settings file. |
| Goose | Add the GA4 MCP server to Goose. Goose uses YAML, calls the command cmd, and calls the environment block envs. All three differ from the usual shape. |
| Kiro | Add the GA4 MCP server to Kiro. Kiro hot-reloads mcp.json on save, so no restart is needed, and it carries per-tool approval settings the other clients do not. |
| Devin Desktop | Add the GA4 MCP server to Devin Desktop, the client formerly named Windsurf. Includes the config path conflict between two live vendor pages. |
| OpenCode | Add the GA4 MCP server to OpenCode. The config is the furthest from the common shape: root key mcp, type local, command as an array, environment not env. |
| DeepSeek Harness | Add the GA4 MCP server to DeepSeek Harness with one entry in your patch layer. Tools then appear as mcp__ga4__get_ga4_data inside the session. |
| Pi | Add the GA4 MCP server to Pi with one mcpServers entry in the agent directory, or with pi mcp add. Tools appear as mcp__ga4__get_ga4_data. |
| OpenClaw | Add the GA4 MCP server to OpenClaw with openclaw mcp add, stored under mcp.servers in ~/.openclaw/openclaw.json. No plugin needed. |
| Hermes | Add the GA4 MCP server to Hermes Agent. The root key is mcp_servers in YAML, not mcpServers in JSON, so a Claude snippet silently adds nothing. |
| ZCode | Add the GA4 MCP server to ZCode. Servers live under mcp.servers in ~/.zcode/cli/config.json, and a competing .agents/mcp.json is skipped entirely, not merged. |
| Antigravity IDE | The Antigravity IDE uses the same mcp_config.json schema as the App and CLI. Manage it from the agent panel's MCP Servers screen, or edit the file directly. |
If your client is not here
It probably still works. The server speaks MCP over stdio, which is the transport every client here uses. Start from the shape used by the client closest to yours, run uvx google-analytics-mcp in a terminal to confirm the server itself is fine, and then find where your client keeps its server list.
The server itself is client-agnostic. It speaks MCP over stdio. The only thing that changes per client is where the entry lives and what the surrounding keys are called.
Next
Whichever client you pick, the credentials and verification steps are the same. Read install for those, then permissions when the first query returns a 403.