Check your website traffic, visitors, pages, referrers, events and funnels from Pirsch analytics.
Read Pirsch web analytics dashboards to see visitors, page views, sessions, referrers, UTM parameters, events, funnels, goals, geographic data, devices, and individual session details. Requires a Pirsch account and OAuth connection.
Try asking Muse: "Show me how many visitors came to my website last week and which pages they visited most."
Source: Found in the official MCP Registry (io.usefulapi/pirsch) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 3 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://pirsch.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Pirsch Analytics is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://pirsch.usefulapi.io/mcpResponse time at the last check: 1534ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
pirsch_list_domainsList 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_domainOne Pirsch dashboard (domain) by id, with its time zone, hostname, role and subscription state. GET /api/v1/domain?id=.pirsch_get_overviewQuick 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_totalsTotals 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_seriesVisitors, 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_growthGrowth 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_visitorsVisitors 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_distributionVisitors 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_durationAverage session duration over time, or average time on page over time, in seconds. GET /api/v1/statistics/duration/session or /duration/page.pirsch_list_pagesTop 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 relativepirsch_list_hostnamesTraffic per hostname. Mostly useful for rollup views that combine several hostnames. GET /api/v1/statistics/hostname.pirsch_list_referrersWhere 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/statipirsch_list_utmVisitors 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_geographyVisitors 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_devicesVisitors 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 orpirsch_get_platformsVisitors on desktop, mobile and unknown platforms, as counts and shares. GET /api/v1/statistics/platform.pirsch_list_eventsCustom 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_breakdownThe 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_pagesThe pages on which an event was triggered, with visitors and views. The event name is required. GET /api/v1/statistics/event/page.pirsch_list_goalsConversion 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_funnelsThe 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_funnelVisitors 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_tagsTag 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_breakdownThe values of one tag key with views and share. The tag filter (the key) is required. GET /api/v1/statistics/tag/details.pirsch_list_sessionsIndividual 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_sessionAll 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_valuesThe 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}.https://pirsch.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Pirsch Analytics to help me. It is a free service with an MCP server at https://pirsch.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 29, 2026, 09:16 UTC) the endpoint was working, answering in 1534ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 27 tools, including pirsch_list_domains, pirsch_get_domain, pirsch_get_overview, pirsch_get_totals. For example, you could ask Muse: "Show me how many visitors came to my website last week and which pages they visited most."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/pirsch)). If you build Pirsch Analytics, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/pirsch-analytics"><img src="https://musedirectory.ai/badge/pirsch-analytics.svg" alt="Pirsch Analytics on musedirectory.ai" width="236" height="40"></a>