Read Pirsch web analytics: visitors, pages, referrers, UTM, events, funnels and sessions. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"pirsch": {
"url": "https://pirsch.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"pirsch": {
"type": "http",
"url": "https://pirsch.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Pirsch client ID and Pirsch client secret.
In Pirsch open Account Settings (all your dashboards) or, on a dashboard you own, Integration Settings, click Add Client, choose the type oAuth and turn off every write scope. The secret is shown once. Access keys (pa_...) cannot read statistics. Your credentials are used only to call the Pirsch API on your behalf; they are never shown to anyone. The Pirsch API needs a paid Pirsch plan.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Pirsch client ID and Pirsch client secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
pirsch_list_domains | read | List domains (dashboards) List the Pirsch dashboards (domains) the OAuth client can read: id, hostname, display name, time zone and role. Use the id as domain_id in every other tool. A dashboard-level client sees one domain; an account-level client sees all. GET /api/v1/domain. |
pirsch_get_domain | read | Get domain One Pirsch dashboard (domain) by id, with its time zone, hostname, role and subscription state. GET /api/v1/domain?id=. |
pirsch_get_overview | read | Get overview Quick overview of a dashboard: visitors, views, growth compared with the previous period, a visitors time series and the number of team members. Cached by Pirsch; takes no date range or filters. GET /api/v1/statistics/overview. |
pirsch_get_totals | read | Get total visitors Totals for a period: visitors, views, sessions, bounces, bounce rate and conversion rate. Not grouped by day, so returning visitors are counted once. GET /api/v1/statistics/total. |
pirsch_get_visitors_time_series | read | Get visitors time series Visitors, views, sessions, bounces and bounce rate per day, week, month or year (see scale). Use it for traffic charts and trends. GET /api/v1/statistics/visitor. |
pirsch_get_growth | read | Get growth rates Growth of visitors, views, sessions, bounces, time spent and conversion rate compared with the previous period of the same length. GET /api/v1/statistics/growth. |
pirsch_get_active_visitors | read | Get active visitors Visitors on the site right now (or in the past n seconds), with the pages they are on and their countries. GET /api/v1/statistics/active. |
pirsch_get_time_distribution | read | Get visitors by time Visitors by hour of the day, by minute (only when from and to are the same day), or by weekday and hour (Monday is 0). Shows when traffic peaks. GET /api/v1/statistics/hours, /minutes or /weekdays. |
pirsch_get_duration | read | Get time spent Average session duration over time, or average time on page over time, in seconds. GET /api/v1/statistics/duration/session or /duration/page. |
pirsch_list_pages | read | List pages Top pages with visitors, views, sessions, bounces, bounce rate and average time on page. type=entry lists landing pages, type=exit lists exit pages. Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/page, /page/entry or /page/exit. |
pirsch_list_hostnames | read | List hostnames Traffic per hostname. Mostly useful for rollup views that combine several hostnames. GET /api/v1/statistics/hostname. |
pirsch_list_referrers | read | List referrers Where visitors come from: referrers (by=referrer) or traffic channels such as Organic Search and Paid Search (by=channel). Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/referrer or /channel. |
pirsch_list_utm | read | List UTM parameters Visitors per UTM source, medium, campaign, content or term. Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/utm/{dimension}. |
pirsch_list_geography | read | List countries, regions, cities and languages Visitors per country, region, city or language. Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/country, /region, /city or /language. |
pirsch_list_devices | read | List browsers, operating systems and screens Visitors per browser, browser version, operating system or screen class (XXL to S). Filters narrow the data (for example country=de, path=~blog). Results are rows with visitors, views, sessions, bounces and relative shares. GET /api/v1/statistics/browser, /browser/version, /os or /screen. |
pirsch_get_platforms | read | Get platform split Visitors on desktop, mobile and unknown platforms, as counts and shares. GET /api/v1/statistics/platform. |
pirsch_list_events | read | List events Custom events with count, visitors, views, conversion rate, average duration and their metadata keys. Use pirsch_get_event_breakdown for the values of one metadata key. GET /api/v1/statistics/events. |
pirsch_get_event_breakdown | read | Get event metadata breakdown The values of one metadata key of one event, with count, visitors and conversion rate. Both event and event_meta_key are required. GET /api/v1/statistics/event/meta. |
pirsch_list_event_pages | read | List pages of an event The pages on which an event was triggered, with visitors and views. The event name is required. GET /api/v1/statistics/event/page. |
pirsch_list_goals | read | List conversion goals Conversion goals with their definition (page pattern, event, targets) and the visitors, views and conversion rate for the period. GET /api/v1/statistics/goals. |
pirsch_list_funnels | read | List funnels The funnels defined for a dashboard, with their steps and step filters. Use a funnel id in pirsch_get_funnel. GET /api/v1/funnel. |
pirsch_get_funnel | read | Get funnel statistics Visitors per funnel step for a period: visitors, share of the first step, drop-off between steps. The filter applies to the first step. GET /api/v1/statistics/funnel. |
pirsch_list_tags | read | List tags Tag keys with views and share. Use pirsch_get_tag_breakdown to see the values of one key. GET /api/v1/statistics/tags. |
pirsch_get_tag_breakdown | read | Get tag breakdown The values of one tag key with views and share. The tag filter (the key) is required. GET /api/v1/statistics/tag/details. |
pirsch_list_sessions | read | List sessions Individual visitor sessions: start, duration, entry and exit page, page views, bounce, country, city, referrer, browser, OS and UTM data. visitor_id is a string (a 64-bit number). Use pirsch_get_session for one session's page views and events. GET /api/v1/statistics/session/list. |
pirsch_get_session | read | Get session details All page views and events of one session in time order. Both ids come from pirsch_list_sessions. GET /api/v1/statistics/session/details. |
pirsch_list_filter_values | read | List filter values The values that exist for a filter in a period, such as all page paths, referrers, countries, browsers or event names. Use it to find valid values before filtering. GET /api/v1/statistics/options/{dimension}. |
pirsch_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
pirsch_request_feature | Request a missing feature Tell usefulapi that the user needs something the Pirsch Analytics tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
pirsch_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Pirsch Analytics tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
pirsch_cancel_subscription | Cancel the Pro subscription Cancel the caller's Pirsch Analytics Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run pirsch_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Pirsch Analytics server only. Subscribe with pirsch_upgrade (it returns a Stripe Checkout link). Cancel any time with pirsch_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running pirsch_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Pirsch Analytics. The server calls the Pirsch Analytics API with your own Pirsch Analytics access, so it sees only the data that your account can see.
The login page asks for your Pirsch client ID and Pirsch client secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Pirsch client ID and Pirsch client secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Pirsch Analytics API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Pirsch Analytics.
All 27 Pirsch Analytics tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Pirsch Analytics server only. Run pirsch_usage_status to see how many calls you used.
Ask the AI to run pirsch_upgrade: it returns a Stripe Checkout link. To cancel, run pirsch_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with pirsch_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.