Every analytics tool with an MCP, compared

Nine analytics tools ship an official MCP server as of September 2026: Lodd, Umami, Rybbit, OpenPanel, PostHog, Google Analytics 4, Amplitude, Mixpanel and Microsoft Clarity. Plausible and Fathom still have community servers only. The May version of this post listed six, and "has an MCP" was enough to stand out. It isn't any more. The useful questions now are whether the server can write or only read, how it authenticates, and whether the MCP is the product or a feature added to a dashboard.

First published in May 2026. Rewritten on 19 September 2026 after Umami, Rybbit and OpenPanel shipped their own servers.

Nine official servers, side by side

Tool counts are each vendor's own number, checked against their docs on 19 September 2026. The PostHog figure is from a count in May and has not been repeated since.

The privacy-first tools caught up

Umami, Rybbit and OpenPanel now each ship an official MCP server, and none of them was in the May version of this post. Umami's is the newest, released in v3.4.0 on 17 September 2026. In May the cookieless, privacy-first tools on this list had community wrappers with four or five tools, and the official servers belonged to the large product analytics suites.

All three kept their dashboard and added the MCP next to it. That is the sensible move for a product with an existing user base, and it means a Umami or Rybbit user no longer has to switch tools to get traffic data into an agent session. It also means the choice between them is now about the details in the sections below, not about who has a server.

Umami: official, read-only, 23 tools

Umami's MCP is a first-party package, @umami/mcp, with 23 read-only tools covering stats, traffic series, top pages and referrers, realtime, events, sessions, funnels, goals, journeys, retention, attribution, revenue, Core Web Vitals and annotations. It runs three ways: hosted at cloud.umami.is/mcp, as an endpoint on a self-hosted instance, or locally over stdio.

{
  "mcpServers": {
    "umami": {
      "command": "npx",
      "args": ["-y", "@umami/mcp"],
      "env": { "UMAMI_API_KEY": "api_<your-cloud-api-key>" }
    }
  }
}

On a self-hosted instance the endpoint is off by default and needs MCP_ENABLED=1. Authentication is an API key in a bearer header, with no OAuth flow, so the client has to support custom headers. The README states that Cloud MCP "has the same subscription requirements" as the Cloud API. Umami is open source and self-hostable, which none of the hosted-only servers on this list can match. There is a longer Umami and Lodd comparison for the rest.

Rybbit lets the agent write

Rybbit's hosted MCP has 39 tools and is the only privacy-first server here with write access. Its own page says "This isn't a read-only feed": the agent can create goals, save funnels, configure sites, identify users and manage organisation members, as well as query traffic and run read-only SQL. The endpoint is app.rybbit.io/api/mcp, and the same endpoint ships with self-hosted installs.

Auth is OAuth in clients that support it, or a revocable API key that can be scoped down to analytics read-only. Destructive tools need an admin or owner role and carry the MCP destructive annotation, so a well-behaved client asks before running them. Whether write access is a feature or a risk depends on how much the agent is trusted with. An agent that sets up its own goal after shipping a signup form is useful. An agent with member management on a shared organisation needs a scoped key.

OpenPanel: 38 tools, seven of them Search Console

OpenPanel hosts a read-only MCP at api.openpanel.dev/mcp with 38 tools by its own count, covering events, sessions, user profiles, B2B groups, funnels, retention, user flow and page performance. Seven of the tools query Google Search Console, including query opportunities and keyword cannibalisation, once GSC is connected in the dashboard. That is unusual for an analytics MCP. With Lodd the same result takes a second MCP server for GSC.

Authentication is a base64 token built from a client ID and secret, passed as a header or a query parameter. There is no OAuth, and write-only clients are rejected. The documented rate limit is 60 requests per minute per client. OpenPanel is a product analytics tool first, with profiles and cohorts at the centre, so it suits an app with logged-in users more than a content site.

PostHog: breadth for a full product stack

PostHog's MCP is the largest by a wide margin, with 446 tools when counted in May 2026 across analytics, feature flags, experiments, error tracking, session recording, surveys and data pipelines. Connecting is free. PostHog's docs note that some tools use LLMs internally and may be billed as PostHog AI spend.

For a team already on PostHog that wants an agent to triage errors, flip flags and check analytics in one session, nothing else covers as much. The cost is that an agent looking for page views has to work through a surface built for a whole product suite, and the query format shows it. Daily page views for the last week:

{"kind": "InsightVizNode", "source": {"kind": "TrendsQuery",
  "series": [{"kind": "EventsNode", "event": "$pageview",
  "custom_name": "Pageviews"}], "dateRange": {"date_from": "-7d"},
  "interval": "day"}}

The same question to Lodd is {"site": "example.com", "period": "7d"}. The PostHog and Lodd comparison covers what that difference costs in context.

GA4, Amplitude and Mixpanel: add the MCP where the data already lives

Google Analytics 4, Amplitude and Mixpanel each have an official MCP server, and the reason to use one is that the data is already there. Google's server has 7 tools: get_account_summaries, get_property_details, list_google_ads_links, run_report, run_funnel_report, run_realtime_report and get_custom_dimensions_and_metrics. Setup needs Python, pipx, two Google Cloud APIs enabled and Application Default Credentials, which is a real barrier outside the GCP ecosystem.

Amplitude and Mixpanel both use OAuth and neither publishes a tool count. Amplitude's covers analytics, experiments, session replay and cohorts. Mixpanel's is hosted and exposes funnels, retention, flows and session replays. Both sit on APIs that were built to serve dashboards, and both work.

Plausible, Fathom and Clarity still limit what an agent can see

Plausible and Fathom have no official MCP server, and Microsoft Clarity's official one is capped at 10 API requests per day. For Plausible, the Sentry-built community server has four tools (get_timeseries, get_breakdown, get_conversions, compare_periods) and is still maintained. It has no funnels and no realtime. Plausible itself now reports referrals from ChatGPT, Perplexity and Claude in the dashboard, which is a different thing from agent access.

Clarity's limits come from Microsoft's own documentation: up to 10 requests per day per project, a maximum of 3 days of data, and up to 3 dimensions per request. An agent can use that for a daily summary and little else. The Clarity comparison and the Plausible comparison have the details.

Where does Lodd fit now?

Lodd is the one tool on this list with no dashboard, where the MCP server is the whole product. The 42 tools cover traffic, timeseries, funnels, breakdowns, custom events, conversion attribution, session paths, actor analytics, annotations, trackable links, a bot report and AI-assistant referrals. It runs hosted at api.lodd.dev/mcp with OAuth, or locally through npx -y @lodd/mcp-server with an API key, and the limit is 1,000 requests per hour.

Responses are compact JSON shaped for a context window, since no dashboard has to render them. Setup is one prompt: "add lodd.dev analytics to this project", and the agent reads llms.txt, handles auth and embeds the script. Analytics data is read-only by design. The agent already has the tools to change the site, and Lodd supplies the signal.

The trade-offs are plain. There are no charts to open in a browser. Lodd is cloud-only and closed source, where Umami and Rybbit can be self-hosted. It is also newer and smaller than everything else here. Free up to 2,500 events a month, then €9.99 a month for 100K, with every tool on both tiers. Setup is in the docs.

Which analytics MCP should you pick?

Pick the server for the tool that already holds the data, unless agent access is the main reason for choosing the tool. A Umami user should enable Umami's MCP. A Rybbit or OpenPanel user should connect theirs. Amplitude, Mixpanel and GA4 users should add the official server and skip a migration. GA4 takes the longest to set up.

• The agent operates the whole product stack (flags, experiments, errors, analytics): PostHog.
• The agent should create goals and funnels as well as read them: Rybbit, with a scoped key.
• Search Console data in the same server: OpenPanel.
• Self-hosted and open source: Umami or Rybbit.
• Nobody will open a dashboard, and the agent is the only reader: Lodd.
• Plausible or Fathom: the community servers handle occasional questions. Agent access is still a gap.

Setup friction, shortest to longest: Lodd (one prompt), Rybbit, Amplitude and Mixpanel (OAuth), Umami and OpenPanel (API key in a header), PostHog (OAuth, then a large tool surface), GA4 (GCP credentials, pipx, two API enables).