d8a .tech

Resources / Blog

Analytics MCP Servers Compared: GA4, Matomo, PostHog, Rybbit, Umami and d8a.tech

data tech team • #analytics#ai#mcp#claude#chatgpt#ga4#matomo#posthog
Feature image

A year ago, “ask your analytics a question in plain English” meant a vendor’s built-in chatbot. Now it means connecting your analytics to the AI chat you already use, Claude, ChatGPT or anything else that speaks the Model Context Protocol (MCP), and asking there.

Almost every web analytics tool has an MCP server by now. They are not the same thing. Some only read reports, some can create dashboards and delete feature flags, and one of the biggest only runs on your laptop. And the hard part is rarely the connection. It’s whether the numbers that come back are right.

What We Compared

We looked at the official MCP server of each tool, or the community servers where there is no official one, from their documentation and directory listings in November 2026:

The full table, with sources and cells we could not confirm, is on our AI-ready analytics page. Here is the short version.

ToolOfficial serverReadsCan changeBefore a change
Google Analytics 4Yes, runs locallyData API reportsNothingNot applicable
MatomoYes, a plugin (2026)Reporting APIGoals and segments, if an admin enables themAdmin turns write tools on; no per-change preview
PostHogYes, hostedInsights and SQLDashboards, feature flags and more, including deletesUp to your AI client
RybbitYes, hosted (paid plans)Stats, sessions, events, SQLSites, goals, funnels, membersScoped API keys; no preview documented
UmamiYes (@umami/mcp)Traffic statsNothingNot applicable
Plausible, FathomCommunity servers onlyDepends on the serverDepends on the serverDepends on the server
d8a.techYes, hostedTables, funnels, journeys, saved insightsProperties, goals, insights, traffic filters, AI contextA full preview, saved only after you approve

GA4: Free, Read-Only, and Local

Google’s own Google Analytics MCP server is open source and, in Google’s words, “available for read requests only”. It runs as a process on your machine with your Google credentials, so it works in Claude Desktop and Claude Code but not in Claude on the web or on your phone, as Count’s setup guide points out.

People who use it like the price and the safety. The complaints are about the answers:

Not everyone is unhappy. A developer writing on Habr connected the GA4 server to Claude Desktop so that Claude would “bring me all the information” instead of the author clicking through the interface, and concluded that with a good prompt it can be “a good marketer for your product” (our translation).

Matomo: Official, Careful, and Read-First

Matomo shipped its MCP Server plugin in 2026, for Matomo Cloud and On-Premise. It is built around reading reports, with optional write tools for things like goals and segments that an admin switches on one by one, capped by a maximum privilege level.

Matomo’s own security FAQ is unusually frank: it rates a read-only setup as low risk and write access as medium risk, because text stored in your analytics, such as a page title, could try to steer the assistant. Its advice is a dedicated Matomo user for MCP with the fewest permissions that work. We think that advice applies to every tool in this list.

PostHog: The Most Complete, With the Most Rope

PostHog’s hosted MCP server does the most: insights, SQL, dashboards, feature flags, experiments and more, with an AI wizard that installs the SDK and the server for you, and a Claude plugin that adds skills on top of the connector. A reviewer on Trustpilot says they plug it into Claude for all their hobby projects and call it amazing.

The flip side is in PostHog’s own docs: write tools include deletes, and PostHog tells you to always review tool calls before they run, because of prompt injection. Whether a change gets reviewed is up to your AI client and your habits, not the server.

Rybbit and Umami: Small Tools, Real Servers

Rybbit has a hosted server on its paid plans that reads stats, sessions and raw events, runs read-only SQL, and can manage sites, goals and funnels. Its docs recommend a scoped API key with only read scopes if you want a read-only setup; out-of-scope calls return a 403.

Umami’s official server is deliberately small: read-only tools over the public API, never touching the database, hosted on Umami Cloud or run with npx.

Plausible and Fathom don’t publish their own servers; community ones fill the gap, with all the maintenance questions that brings.

What Actually Goes Wrong

Across the write-ups, the same three problems come back, and none of them is about MCP itself:

  1. The model guesses what a metric means. If the server hands it a nested schema and 200 similarly named fields, it will pick one, confidently.
  2. Nobody sees the query. An answer without the date range, filters and metric behind it can’t be checked.
  3. Writes without a checkpoint. A server that can change settings or delete things is only as safe as the client’s confirmation dialog, and prompt injection through analytics data is a documented risk.

Our Take, and Where d8a.tech Fits

We built the d8a.tech MCP server around those three problems, and we’re biased, so here is exactly what it does:

It works in Claude, ChatGPT and any MCP client, read-only by default, for data in the d8a.tech cloud. It doesn’t work with your own warehouse or a self-hosted install yet; there, point your own tools at your tables.

Before You Connect Any of Them

If you want to try ours, sign up for the free Cloud Dashboard, add d8a.tech from the connectors in Claude or ChatGPT, and ask for this week’s review. If a cell in our comparison is out of date, tell us and we’ll fix it.

← Back to Blog

See d8a.tech on your own stack.

Talk to us about your architecture, terms, a partnership or sponsored development. Or start with free Cloud and evaluate it yourself.