GAGA4 MCPv2.11.9

Plugins

A plugin is a manifest that tells a client how to launch the server and what values it needs. It is not a different server. It is the same uvx google-analytics-mcp with the configuration attached, so the client can install and prompt for the two values in one flow instead of asking you to edit a JSON file.

Two clients support a plugin bundle today.

BundleWhat the page covers
Claude Code bundleThe Claude Code plugin bundle declares the GA4 MCP server and its two required settings, so Claude Code can install the server and prompt for the values.
Gemini extensionThe Gemini extension declares the GA4 MCP server and the two settings Gemini CLI prompts for, so the server installs without hand-edited JSON.

When a plugin is worth it

If you install the server once, on one machine, the plain config entry is simpler and this page adds nothing. A plugin pays off when you want the client to ask for GA4_PROPERTY_ID and the credentials path itself, or when you are distributing the setup to other people and do not want them editing config files.

What is inside

Both bundles carry the same two declarations:

json
{
  "mcp": {
    "command": "uvx",
    "args": ["google-analytics-mcp"]
  },
  "settings": [
    { "name": "GA4_PROPERTY_ID", "required": true, "type": "string" },
    { "name": "GOOGLE_APPLICATION_CREDENTIALS", "required": true, "type": "string" }
  ]
}

The settings array is what makes the client prompt. The mcp block is what it launches. Everything else is metadata — name, version, license, repository.

Next

If you would rather not use a bundle, the per-client guides show the raw config: Claude, Gemini CLI, or the full client list.