mcpbeat Sign in

Google Analytics MCP Server

answering

Google Analytics is answering right now. Last checked 1 min ago.

Usuários, sessões, páginas e origens do tráfego do seu site

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
263 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Google Analytics every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add google-analytics --transport http https://google-analytics.mcp.myagents.click/mcp
Settings → Connectors → Add custom connector, then paste this address
https://google-analytics.mcp.myagents.click/mcp
~/.codex/config.toml
[mcp_servers.google-analytics]
url = "https://google-analytics.mcp.myagents.click/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "google-analytics": {
      "url": "https://google-analytics.mcp.myagents.click/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "google-analytics": {
      "type": "http",
      "url": "https://google-analytics.mcp.myagents.click/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://google-analytics.mcp.myagents.click/mcp streamable-http sign-in 217 ms 1 min ago

Alternatives to Google Analytics

same job, measured the same way
Google Search Console
by myagents

Cliques, impressões e posição do seu site na Busca do Google

answering
Google_analytics
by pipeworx-io

Google Analytics MCP Pack

46 tools answering
Google Gsc
by mharnett

Google Search Console MCP: search analytics, URL inspection, site management.

81 installs/wk local only
Google Analytics 4
by getmcpads

Google Analytics 4 MCP server: 27 read tools, no write tools.

37 installs/wk local only
Google Search Console MCP
by scalably

Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.

171 installs/wk local only
Google Search Console MCP
by a1-x-tech

MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.

33 installs/wk local only
Google Search Console
by sarahpark

Google Search Console MCP server — search analytics, URL inspection, and sitemaps

73 installs/wk local only
Google Search Console
by ni-c

MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection

47 installs/wk local only

Google Analytics — questions

Answers built from our own checks of this server.

Why is there no tool list for Google Analytics?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Google Analytics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 263 ms. The bar chart above shows every period we have measured.
How do I connect Google Analytics?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Google Analytics?
No API key is involved. Google Analytics answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Google Analytics?
It answers our handshake in 263 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.