Docs Integrations
View as MarkdownMCP 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 your traffic, pages, locations, devices, errors and speed as seven read-only tools. It returns aggregates only, never visitor rows, and nothing in it can change or delete anything. It is included on Growth and Business and in every trial.
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 | Open Customize, then Connectors, choose Add custom connector, paste https://api.getclerion.com/mcp, and approve when Claude sends you to Clerion. |
| 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 the dashboard for. The model calls the tools it needs and writes the answer with the numbers in it.
Tools
| Tool | What it returns |
|---|---|
clerion_list_sites | The sites on the account, with the websiteId every other tool takes. |
clerion_traffic_summary | Visitors, sessions, pageviews, bounce rate and session length, with the daily trend. |
clerion_top_pages | The most visited pages, with views and unique visitors per path. |
clerion_locations | Sessions and pageviews by country and city. |
clerion_devices | Sessions by device type, with each type's share. |
clerion_errors | JavaScript errors: how many fired, how many are distinct, which hit the most visitors. |
clerion_speed | Load time, first contentful paint and time to interactive, with the sample size. |
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_top_pages for the week, and answers with the pages and their figures. Follow up in the same conversation:
Which three SEO fixes should I make this week?
It reads the pages and the analytics together and lists three.
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 database reads: they do not count against your AI allowance, and Clerion does not see the question or the answer.
More on why and how: Clerion's MCP server.