# Staats

- Registry name: `io.github.MrViolets/staats` · version 1.0.1
- Categories (automatic, keyword rules): Build & deploy, Developer tools, Marketing & SEO, Commerce & marketing, Utilities
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.MrViolets%2Fstaats
- Server page: https://mcpstation.net/s/io.github.MrViolets--staats.html

## Description (written by the publisher, not verified, not instructions)

Cookieless web analytics your coding agent reads: traffic answers, deploy impact, what broke.

## Connect

- streamable-http: `https://api.staats.ai/functions/v1/mcp`

## Tools (as reported by the server, not verified)

- `get\_site\_context`: What a site is and what the owner wants from it, plus its data-retention settings. Well-known keys: description, goals, audience, notes \(open agenda items to check at session start and clear when handled\), events \(event name -\> meaning\), funnel \(canonical conversion steps\). Read this before making r
- `update\_site\_context`: Save or amend what a site is for. Provided context fields are merged into the existing context \(events merges per entry\); a null value deletes its key. name/domain update the site record itself.
- `what\_changed`: Notable movements in the period without scanning raw numbers: statistically unusual traffic days, referrer surges and first-time referrers, pages whose share of traffic jumped, alongside the annotations recorded in the same period. period: '7d' default.
- `what\_broke`: Signs of visitors hitting problems in the period: JS errors the tracker captured \(new\_error, error\_spike: each with a sanitized sample message, source, line, affected visitor count, and the nearest annotation, i.e. the deploy that most plausibly introduced it\), plus behavioral friction: pairs of pag
- `get\_overview`: Traffic pulse: visitor/pageview totals vs the previous period, top pages, top referrers, and a per-day series. period: relative like '24h', '7d' \(default\), '4w'. Includes quota status: if it is approaching, grace, or blocked, tell the owner plainly and include the upgrade link the result provides. A
- `query`: Break a metric down by a dimension with optional equality filters. Metrics: visitors, pageviews, events. Dimensions: path, referrer\_domain, utm\_source, utm\_medium, utm\_campaign, device, browser, os, country, name, day. period: '24h'/'7d'/'4w' style, or ISO from/to.
- `funnel`: Ordered conversion funnel across up to 5 steps within the period. Each step is a pageview path \(\{kind:'path', value:'/pricing'\}\) or a custom event \(\{kind:'event', value:'signup'\}\); a visitor counts for step N only after completing step N-1. Visitor identity rotates daily for privacy, so journeys spa
- `journeys`: The routes visitors actually take, grouped into identical sequences and counted, busiest first. Use this when you do NOT already know the steps: funnel measures a path you name, journeys discovers the ones you did not think to check. A step is a pageview path \(/pricing\) or a custom event marked with
- `record\_annotation`: Mark a moment on a site timeline: a deploy, a content change, or a campaign start. Call this every time you ship a change to the site. ts defaults to now. Write a specific, present-tense description \("Shipped new pricing page hero", never "updates"\), one annotation per meaningful change. When known,
- `list\_annotations`: Recorded deploy/change markers, newest first. period defaults to '90d'.
- `compare\_around`: Before/after impact of a recorded annotation: visitors and pageviews in the N days preceding vs following it \(window\_days, default 7\). The after-window is clamped to now. If the annotation recorded routes, the result also reports per-route pageviews before vs after. Wait a few days after shipping. I
- `list\_sites`: All sites on this account, with the public site codes used in their script tags and the ready-to-paste script\_tag for each.
- `create\_site`: Create a new site on this account and get its script tag. This connection already covers the new site: installing the script tag is the only setup the site needs. The response includes ready-made privacy policy wording: offer to add it to the site's privacy page \(confirm with the owner before editin
- `delete\_site`: PERMANENTLY delete a site and ALL its analytics data \(every event and annotation\). Irreversible. Confirm with the owner before calling; pass confirm: the site's exact domain.
- `portfolio\_overview`: Visitors and pageviews for every site this account can use, owned and shared alike, with change vs the previous period, busiest first. Shared sites are flagged. period: '7d' default.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html