Integrations
MCP server
Clerion runs an MCP server at https://api.getclerion.com/mcp. Connect Claude, Cursor or any client that speaks MCP over HTTP, and it reads every report in Clerion as 27 tools: traffic, sources, pages, flow, events, revenue by source, errors, speed, tracking health, SEO and the briefing. A 28th, clerion_connect_site, adds a site, so a new account can connect from the chat. It returns aggregates only, never visitor rows, and nothing in it can change or delete anything. It is included on every plan, free included. The questions run on your own model, so they never count against your AI allowance; only the briefing, signals and audience tools use it, the same as in the app.
Connect a client
- In the Clerion dashboard, open Your model. It shows a command for clients that take a key, the address for Claude's connector, and your key with Replace key beside it.
- Add Clerion to your client:
| Client | How |
|---|---|
| claude.ai, Claude Desktop, Cowork | Add Clerion from the connectors directory and approve when Claude sends you to Clerion. Or open Customize, then Connectors, choose Add custom connector and paste https://api.getclerion.com/mcp. |
| Claude Code | Run the command shown on the Your model screen in your terminal. |
| Cursor and other clients that take a key | Add an HTTP MCP server at https://api.getclerion.com/mcp with an Authorization header of Bearer and your key. |
Claude Code
Paste the command from Your model. It has this shape, with your own key:
claude mcp add --transport http clerion https://api.getclerion.com/mcp \
--header "Authorization: Bearer clm_..."
Cursor
Add the server to .cursor/mcp.json in your project, or the global one:
{
"mcpServers": {
"clerion": {
"url": "https://api.getclerion.com/mcp",
"headers": { "Authorization": "Bearer clm_..." }
}
}
}
Any other client
Point it at https://api.getclerion.com/mcp over HTTP with an Authorization: Bearer clm_... header, or, if it supports OAuth, add the address alone and approve the connection when it sends you to Clerion.
- Ask the question you would have opened Clerion for. The model calls the tools it needs and writes the answer with the numbers in it.
Tools
Every tool but clerion_connect_site only reads, and returns the figures the app shows for the same window. There are 28, in five groups.
Arguments
| Argument | Meaning |
|---|---|
range | The window: today, yesterday, last7days, last30days, last90days, thisMonth, lastMonth, or custom:YYYY-MM-DD_YYYY-MM-DD. Defaults to last7days. Windows that reach past your plan's retention are refused with a message that says so. |
websiteId | One site, from clerion_list_sites. Leave it out to read every site on the account together. clerion_seo_overview requires it; clerion_live, clerion_tracking_health and clerion_seo_overview take no range. |
goal | clerion_conversion_insights only, required: the event name that counts as the win, such as purchase or signup. The names are in clerion_custom_events. |
Sites and traffic
| Tool | What it returns |
|---|---|
clerion_list_sites | The sites on the account, with the websiteId every other tool takes. A new account also sees the demo site, Parsel, marked demo, so the tools can be tried before your own traffic arrives. With no site of its own, the demo entry tells the model so, and it asks for yours. |
clerion_connect_site | Adds a site by its address (url, such as example.com). Returns the one-line snippet, where it goes on your site builder, and what the homepage already shows from outside: title, description, headings, robots.txt rules for AI crawlers, noindex, text without JavaScript. Calling it again with the same address returns the same site. In an editor, the model can add the snippet to your code itself. |
clerion_traffic_summary | Visitors, sessions, pageviews, bounce rate and session length, with the daily trend. |
clerion_traffic_sources | Each channel (search, social, direct, referral, AI assistants, campaigns) and the referrers inside it, with sessions and conversions. |
clerion_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. |
clerion_campaigns | UTM campaigns, sources and mediums, with sessions and conversions. |
clerion_live | Who is on the site right now and the pages they are on. |
clerion_bots_blocked | How many bot visits were refused, and which kinds. |
clerion_tracking_health | Whether the snippet is still reporting. Names pages that were busy over the last two weeks and have recorded nothing for three days, or says the whole site has gone quiet. Takes no range: the windows are fixed. With too little traffic to tell, it says so, and that is not a pass. |
What visitors do
| Tool | What it returns |
|---|---|
clerion_top_pages | The most visited pages, with views and unique visitors per path. |
clerion_entry_exit_pages | The pages visits start on and the pages they end on. |
clerion_user_flow | The paths visitors take between pages, the top paths, and where people leave. |
clerion_engagement | Scroll depth, time on page and active time per page. |
clerion_interactions | Outbound links, file downloads, form submissions and clicked elements, each with a count. |
clerion_locations | Sessions and pageviews by country and city. |
clerion_devices | Sessions by device type, with each type's share. |
clerion_browsers | Sessions by browser and operating system. |
Conversions and customers
| Tool | What it returns |
|---|---|
clerion_custom_events | Every custom event: counts over time, pages, devices, countries, and revenue for events with a value. |
clerion_funnel | The funnel drawn from your custom events: visits at each step and the rate that went on to the next. |
clerion_conversion_insights | Which pages, sources and devices lift or hurt conversion to one event (goal), against the previous window. |
clerion_customers_and_causes | Revenue by source, the exit question's answers, each deploy set against the day before, and rage clicks. Each part states its own limits. |
Whether the site is working
| Tool | What it returns |
|---|---|
clerion_errors | JavaScript errors: how many fired, how many are distinct, which hit the most visitors. |
clerion_error_log | The error log with ERROR, WARN and INFO levels, grouped by message. |
clerion_speed | Load time, first contentful paint and time to interactive, with the sample size. |
clerion_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. Requires websiteId. |
Written by Clerion
These three return the pieces Clerion writes in the app. They come back from the last time they were written; if the answer says generating or needsGeneration, call again in a minute. They count toward the AI allowance the same way as in the app.
| Tool | What it returns |
|---|---|
clerion_briefing | The written briefing for the window: what changed, why, and the one fix to make first. |
clerion_signals | What changed, ranked by impact against your goal, with the figures behind each. |
clerion_audience | Who the visitors are, written from the figures. |
What a question looks like
Ask the way you would ask a colleague. The model picks the tools:
Where did visitors leave last week?
The client calls clerion_list_sites for the site id, then clerion_user_flow and clerion_entry_exit_pages for the week, and answers with the pages and their figures. Follow up in the same conversation:
Which source brought the most paying customers this month, and why did people leave the pricing page?
It reads clerion_customers_and_causes for the month and answers with revenue per source and the exit answers.
Did Tuesday's release make anything worse?
It reads clerion_customers_and_causes for the deploy, clerion_errors and clerion_speed for the days around it, and says what moved.
Write the traffic paragraph of my investor update.
It reads clerion_traffic_summary, clerion_top_pages and clerion_ai_referrals and writes the paragraph with the figures in it.
Your key
The key starts with clm_. The same key sends Deploy markers from CI. Replace key retires the old key and every OAuth connection at once, everywhere, on the next request.
Tool calls are reads of the same figures the app shows and do not count against your AI allowance, except clerion_briefing, clerion_signals and clerion_audience, which return the written pieces the app also writes and count the same way there. Clerion does not see the question or the answer.
More on why and how: Clerion's MCP server.