What it does
Breakdown of visits by browser, os, device_type, or country (country empty in MVP). Volume metric — counts include AI-mediated human browsing (ai_user_action).
Example prompts
Ask Claude (or any MCP client connected to mcp-analytics) something like:
Break down visits by browser for mysite.com last 7 days.
The client will pick breakdown automatically based on the prompt and your account's available sites.
Arguments
| Name | Type | Required | Description / Default |
|---|---|---|---|
site_id |
string | required | Site identifier from list_sites (8-character base32, e.g. 'wjxayhdd'). |
dimension |
string enum: browser, os, device_type, country |
required | Which dimension to break down visits by. 'country' is reserved for the MaxMind GeoIP integration on the roadmap, currently returns empty. |
period |
string | optional |
Time window. Keywords: today, yesterday, last_7_days, last_30_days, last_90_days, last_12_months. Or a custom date range YYYY-MM-DD..YYYY-MM-DD (inclusive).
default: last_7_days
|
limit |
integer | optional |
Maximum number of rows to return. Capped at 1000 server-side.
default: 10
|
How to call it directly
If you're integrating from your own code rather than a chat client, this is the JSON-RPC payload:
curl -X POST https://mcp-analytics.com/mcp \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "breakdown",
"arguments": {
"site_id": "abc12345",
"dimension": "browser"
}
}
}'
Token comes from /settings after you sign up. Replace any required arguments above.
Related tools
list_sites: List all sites on the authenticated account.top_timezones: Top IANA timezones (Europe/Berlin, America/New_York, ...) of visitors.event_details: Details for one event.list_events: All event names with counts (includes 'pageview' and custom events).get_account: Account info — email, current plan, total active sites, total_hits_this_month (across all sites), plan_limit, and api_token_first_chars (first 10 chars of the legacy API token, for identification only — not enough to authenticate).