Simple Analytics

@simple-analytics show me the aggregated stats for myapp.com over the last 30 days

Here's the traffic overview for myapp.com (last 30 days): 12,450 unique visitors, 28,300 pageviews, 2.27 pages per session, average session duration 3m 42s, bounce rate 48%. Top referrers: organic search (62%), direct (24%), twitter.com (8%). Most visited pages: /pricing (4,200 views), /docs (3,800 views), /blog/new-feature (2,100 views). This data reflects the aggregated metrics Simple Analytics collected during the period.

This example uses the aggregated stats endpoint, which returns high-level metrics without exposing individual visitor data. Requires a valid API key with read access to the specified website. The MCP returns summary data only—raw event-level details require the export tool instead.

@simple-analytics export the raw pageview data for blog.example.com from March 1-15 as JSON

Export initiated for blog.example.com (March 1-15, 2025). The JSON file contains 8,432 raw pageview records with fields: timestamp, path, referrer, country, device type, browser. Each record represents one page load. Download link valid for 24 hours. Note: event tracking data (button clicks, form submissions) requires a separate export request if you've configured custom events.

This example demonstrates the raw data export capability, useful for custom analysis or feeding into other tools. Exports can be large—CSV format may be more efficient for high-traffic sites. API key must have export permissions. The MCP triggers the export but doesn't parse the resulting file; you'll need to download and process it separately.

@simple-analytics list all websites in my account, then summarize which ones had traffic drops this month compared to last month

Found 5 websites in your Simple Analytics account: myapp.com, blog.example.com, docs.example.com, staging.myapp.com, landing.newproduct.io. Comparing February to March traffic: myapp.com is up 12%, blog.example.com down 23% (worth investigating—content calendar issue?), docs.example.com roughly flat, staging.myapp.com down 89% (expected for staging environment), landing.newproduct.io up 340% (launch effect). The blog drop stands out as the main concern—recent posts may be underperforming or referral sources shifted.

This example chains two MCP capabilities: listing websites (admin API) and fetching stats for each, then uses the AI to synthesize a comparative analysis. Requires admin-level API key. The month-over-month comparison logic happens in the AI layer, not the MCP itself—Simple Analytics returns point-in-time metrics, so the assistant calculates deltas and interprets trends.

When Simple Analytics beats Google Analytics for small teams

An 8-person startup runs a weekly growth sync where the founder, two engineers, and the marketing lead review traffic trends. They need pageviews, bounce rate, and top referrers—not the 47-metric dashboard Google Analytics throws at them. Simple Analytics wins here because the 'Get aggregated website stats' tool returns exactly those core metrics in one call, and the API key auth means no OAuth dance every time someone new joins the channel. The trade-off: if you need funnel analysis or user cohorts, Simple Analytics stops short. But for teams under 15 people who just want to answer 'are we growing?' in under two minutes, this MCP is the right call. Set it up once, run the same query every Monday, and move on.

Using raw pageview exports to trace support spikes

A 12-person SaaS company sees a 40% jump in support tickets about a specific feature. The support lead suspects a docs page is confusing users, but needs proof before rewriting it. The 'Export Raw Data Points' tool pulls a CSV of every pageview and event for the last two weeks, filtered to that docs URL. The support lead drops it into a spreadsheet, cross-references ticket timestamps, and confirms that 68% of users who hit that page within 10 minutes of signup later file a ticket. That's enough evidence to prioritize a rewrite. The limitation: if your site logs over 100k pageviews a month, the CSV export gets unwieldy and you'll want a proper data warehouse. But for mid-traffic sites where one person owns support analytics, this MCP closes the loop between traffic and tickets in under an hour.

When you manage 4+ marketing sites and need cross-site benchmarks

A 6-person agency manages landing pages for four clients, all tracked in one Simple Analytics account. Every Friday, the account manager needs to compare traffic across sites to decide where to focus content efforts next week. The 'List Websites' tool returns all four sites, then the 'Get aggregated website stats' tool pulls last week's visitors and bounce rate for each in a loop. The manager drops the results into a shared doc, highlights the site with the worst bounce rate, and assigns a content audit. The catch: if you need per-page breakdowns or conversion tracking, you'll hit the tool's ceiling fast. But for agencies or portfolio companies where the question is 'which site needs attention?' rather than 'which page is broken?', this MCP gives you the answer in three API calls and no dashboard login.