ahel
Start free

Staats MCP Server

MCP serverDatabases & data

staats is cookieless web analytics that your AI can read directly. Once added, you can ask about your site's traffic, see how a deploy affected it, and find out what broke. It gathers this data without using cookies.

Available today. Use it from your connected AI after setup.

After adding staats, ask your AI a question about your traffic, a recent deploy, or something that broke. Setup details are in the repository at github.com/MrViolets/staats-mcp.

Then ask your AI: use Staats MCP Server to get site context

What your AI can do with it

  • Answer questions about your website traffic
  • Show how a deploy affected traffic
  • Point out what broke
  • Read your analytics without cookies

From the project's README

As published by mrviolets/staats-mcp in README.md.

Cookieless web analytics your coding agent reads. No dashboard: your agent answers traffic questions, marks deploys, measures before and after impact, and flags errors and visitor friction, all over one MCP connection.

This is the public home of the hosted Staats MCP server. The server runs at Staats, there is nothing to install.

Connect

Sign in at staats.ai (free tier: 10,000 monthly events, 1 site, all tools). Your account view gives you a one-line connect snippet with your key embedded:

# Claude Code
claude mcp add --scope user --transport http analytics "https://api.staats.ai/functions/v1/mcp/YOUR_ACCOUNT_KEY"

Cursor, Windsurf, Codex, and raw URL snippets are in the MCP docs. Clients that prefer header auth can send Authorization: Bearer YOUR_ACCOUNT_KEY to https://api.staats.ai/functions/v1/mcp.

One connection covers every site on your account, current and future.

Tools

14 tools, including:

  • get_overview, query, funnel, journeys: traffic answers with statistical honesty
  • record_annotation, compare_around: mark deploys, measure before/after impact
  • what_changed, what_broke: notable movements, JS errors, and visitor friction, attributed to the nearest deploy
  • create_site, list_sites, site context tools: your agent sets up new sites itself

Unauthenticated connections get initialize and tools/list, so you can inspect the full tool surface before creating an account.

Tracking

One script tag per site, ~1.5 KB compressed, no cookies, no personal identifiers, no consent banner needed:

<script defer data-site="YOUR_SITE_CODE" src="https://www.staats.ai/s.js"></script>

Custom events via data-staats attributes or window.staats('event_name'). Passive JS error capture included on every tier.

Links

Tools it offers (15)

What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • get_site_context
  • update_site_context
  • what_changed
  • what_broke
  • get_overview
  • query
  • funnel
  • journeys
  • record_annotation
  • list_annotations
  • compare_around
  • list_sites
  • create_site
  • delete_site
  • portfolio_overview

Signals

Last commit
Sep 2026
Advanced
Delivery
staats MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
io-github-mrviolets-staats
Source
github.com/mrviolets/staats-mcp
Hosted endpoint
https://api.staats.ai/functions/v1/mcp

github.com/mrviolets/staats-mcp

More in Databases & data

mcp
MCP server · aioproductospg-aiguide
MCP server · timescaleanythingmcp
MCP server · helpcode-aibitview
MCP server · bitcoinresearchkitmcp-server
MCP server · 78degreesEmail and Address Check
MCP server