# Staats Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Staats

Privacy-first web analytics for your site: traffic trends, deploy impact, and error detection.

- Record: https://musedirectory.ai/connector/staats
- Category: Research & Data
- Developer: MrViolets (https://www.staats.ai)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 673ms, checked 2026-09-28T07:45:55Z
- Endpoint: https://api.staats.ai/functions/v1/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-25T03:16:29Z)
- Source: Found in the official MCP Registry (io.github.MrViolets/staats) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.MrViolets%2Fstaats

Staats is a cookieless analytics platform that tracks visitor behavior, page performance, and conversion funnels. Muse can query traffic summaries, identify broken pages or JS errors after deploys, discover visitor journeys, and compare metrics before and after site changes.

Example request: "Show me what changed in my website traffic this week and whether my latest deploy caused any errors."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Staats to help me. It is a free service with an MCP server at https://api.staats.ai/functions/v1/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.

Tools:
- 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 
- 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 fr
- 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 th
- 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 priv
- 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 cust
- 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
- 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 da
- 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
- 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.

Screening checks:
- MCP handshake: pass (Answered in 523ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.staats.ai, www.staats.ai not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (15 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 34 days ago)
- AI review of purpose and tool behavior: pass (No concerns)