Web analytics MCPYour analytics, inside your model.

Start 14-day trial Read the docs

28 tools for Claude, Cursor or any MCP client. Hosted, read-only apart from adding a site, on every plan.

Claude Desktop, connected to Clerion. The person asks where visitors left last week. Claude calls Clerion, answers that most left from the homepage, and shows the pages with their views and visitors. They ask for three things to improve the site’s SEO this week, and Claude lists three fixes.

Claude Desktop, asking where visitors left last week.

Why over MCP

Clerion’s own assistant does the daily reading. MCP is for when your own model should read the same numbers, under your account and your rules.

You choose the model

Claude today, something else next year. Clerion serves the same 28 tools to any client that speaks MCP, so changing the model changes nothing about your analytics.

Clerion is not in the conversation

A tool call is a database read. Clerion returns the figures and nothing more. It does not see the question or the answer, and none of it counts against your AI allowance.

Reads, and one that adds a site

27 tools read: counts and averages per site and date range, never visitor rows. One adds a site, so a new account can connect from the chat. Nothing in the protocol can change a setting or delete a number.

Getting started

Nothing to install. The server is hosted.

  1. 01Open MCP in ClerionStart a trial, paste the one-line tag, then open MCP. It holds a command, an address and your key.
  2. 02Add Clerion to your clientAdd the connector in Claude, run the command in Claude Code, or paste the address and key into Cursor.
  3. 03AskAsk what you would have opened Clerion for. The model calls the tools and answers with the numbers.
claude.ai, Claude Desktop, CoworkAdd the connector

Find Clerion in the connectors directory, or add a custom connector with this address. Claude sends you to Clerion to approve.

https://api.getclerion.com/mcp
Claude Code, Cursor, any client with a keyRun the command

Copy it from the MCP screen in Clerion, where it carries your key. In Cursor, add the same address with a Bearer header.

claude mcp add --transport http clerion https://api.getclerion.com/mcp --header "Authorization: Bearer clm_your_key"

The setup in claude.ai: Customize, Connectors, Add custom connector. The address is typed in, Claude detects sign-in, Clerion asks whether Claude may read your analytics, Approve, and the connector lists the Clerion tools.

The setup in claude.ai, start to finish.

What the model can read

27 tools read counts and averages, never visitor rows. One adds a site.

Sites4
list_sites

The sites on the account, with the websiteId every other tool takes.

connect_site

Adds a site by its address and returns the one-line snippet, where it goes on your builder, and what the homepage already shows search engines and AI assistants.

tracking_health

Whether the snippet is still reporting: pages that were busy and have recorded nothing for three days, or the whole site gone quiet. Says so when there is too little traffic to tell.

live

Who is on the site right now and the pages they are on.

Traffic10
traffic_summary

Visitors, sessions, pageviews, bounce rate and session length, with the daily trend.

top_pages

The most visited pages, with views and unique visitors per path.

ai_referrals

Visits sent by AI assistants: sessions and conversion per assistant against everyone else, the pages they landed on, and the change from the previous window.

traffic_sources

Each channel (search, social, direct, referral, AI assistants, campaigns) and the referrers inside it, with sessions and conversions.

campaigns

UTM campaigns, sources and mediums, with sessions and conversions.

entry_exit_pages

The pages visits start on and the pages they end on.

locations

Sessions and pageviews by country and city.

devices

Sessions by device type, with each type’s share.

browsers

Sessions by browser and operating system.

bots_blocked

How many bot visits were refused, and which kinds.

Behaviour7
user_flow

The paths visitors take between pages, the top paths, and where people leave.

engagement

Scroll depth, time on page and active time per page.

interactions

Outbound links, file downloads, form submissions and clicked elements, each with a count.

funnel

The funnel drawn from your custom events: visits at each step and the rate that went on to the next.

custom_events

Every custom event: counts over time, pages, devices, countries, and revenue for events with a value.

conversion_insights

Which pages, sources and devices lift or hurt conversion, against the previous window.

customers_and_causes

Revenue by source, the exit question's answers, each deploy set against the day before, and rage clicks.

Health4
errors

JavaScript errors: how many fired, how many are distinct, which hit the most visitors.

error_log

The error log with ERROR, WARN and INFO levels, grouped by message.

speed

Load time, first contentful paint and time to interactive, with the sample size.

seo_overview

One site's pages as a search engine or an assistant reads them: titles, descriptions, headings, schema, each page's score and what to fix.

Reading3
briefing

The written briefing for the window: what changed, why, and the one fix to make first.

signals

What changed, ranked by impact against your goal, with the figures behind each.

audience

Who the visitors are, written from the figures.

How your data is kept

Clerion holds aggregates on EU infrastructure and nothing else. It never sees the question or the answer, and your model never sees a visitor. How it works in the code.

Where the numbers go

From your site to Clerion's EU servers to the model you connected. That is the whole route. There is no visitor data to hand over, because Clerion never stored any.

How Clerion keeps data ›

One key, replaced in one click

The old key and every token issued against it stop on the next request, on every server. Access is yours to give and yours to end.

Questions about access ›

Claude asks before it reads

In claude.ai, Claude Desktop or Cowork, Clerion is a custom connector. Claude finds the sign-in on its own and sends you to Clerion, where one screen says exactly what it will read. No key is ever pasted into a web page.

Getting started ›

Other analytics MCP servers

Matomo’s you host yourself. Google’s runs on your machine with a Cloud project behind it. Amplitude’s is sized for product teams. Clerion’s is hosted, read-only and on every plan. The servers compared.

Questions

Clerion already has an assistant. Why MCP?
Use both. Clerion's assistant writes the daily briefing; MCP puts your own model on the same numbers, next to your code and docs.
What is an MCP server?
The other end of the open standard AI clients use to call tools. Clerion's turns your analytics into 28 tools the model reads itself.
Which clients work with it?
Anything that speaks MCP over HTTP. Claude Code and Cursor take the key; claude.ai, Claude Desktop and Cowork add the address as a custom connector.
What can the model read?
Aggregates only: traffic, pages, locations, devices, errors and speed. Clerion stores no visitor rows to hand over.
Where do my numbers go?
From Clerion's EU infrastructure to the model you connected, and nowhere else. Clerion never sees the question or the answer.
Which plans include it?
Every plan, free included. Your questions run on your own model, so they don't use Clerion's AI allowance.
How do I revoke access?
Choose Replace key under MCP. The old key stops working on the next request.

Included on every planYour questions run on your own model.

Start 14-day trial