GAGA4 MCPv2.11.9

Connect Kiro IDE to Google Analytics 4

Kiro reads MCP servers from mcp.json and reloads the file the moment you save it. That is the main practical difference from the rest of this set — you will not be restarting the editor.

Copy-paste analytical prompts

Ask Kiro directly in the chat panel:

  • Weekly performance overview: "Compare activeUsers, sessions, and engagementRate over the last 7 days against the previous 7 days."
  • AI referral audit: "Show me sessions, bounceRate, and keyEvents from ChatGPT, Claude, and Perplexity over the last 30 days."
  • Content drop-off triage: "List top 10 pages by screenPageViews where engagementRate is below 40%."
  • Acquisition channels: "Break down sessions and keyEvents by sessionDefaultChannelGroup for the last 14 days."
  • Realtime traffic check: "Run a realtime report showing active users and top pages over the last 30 minutes."

Where the file lives

  • Workspace: .kiro/settings/mcp.json inside the project.
  • User: ~/.kiro/settings/mcp.json, applied everywhere.

Workspace scope wins when both exist.

The entry

json
{
  "mcpServers": {
    "google-analytics": {
      "command": "uvx",
      "args": ["google-analytics-mcp"],
      "env": {
        "GA4_PROPERTY_ID": "123456789",
        "GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/key.json"
      },
      "disabled": false,
      "autoApprove": ["list_properties", "search_schema", "get_ga4_data"]
    }
  }
}

The root key is mcpServers. The three optional keys are Kiro-specific:

  • disabled — set true to keep the entry but stop it launching.
  • autoApprove — tool names that run without a confirmation prompt. For a read-only analytics server there is no reason to confirm each call.
  • disabledTools — the inverse. Useful for hiding check_for_updates or setup_ga4_access from an agent you want focused on reporting.

Kiro also expands environment placeholders, so a credentials path can come from the shell:

json
"env": {
  "GA4_PROPERTY_ID": "123456789",
  "GOOGLE_APPLICATION_CREDENTIALS": "${GOOGLE_APPLICATION_CREDENTIALS}"
}

From the CLI

bash
kiro-cli mcp add --name google-analytics --scope global --command uvx --args google-analytics-mcp --env GA4_PROPERTY_ID=123456789

--args takes one argument per flag, so a server with several arguments needs the flag repeated rather than a single space-separated string.

Verify

Save the file, then ask:

text
List my GA4 properties.

The server should appear without a restart. If it does not, check the MCP servers panel — Kiro reports a launch failure there rather than failing silently, which it can do because it is watching the process rather than reading a file once.

Next

Setup for the two values, permissions for the 403 that means the service account is not on the property.