English Français العربية

Staats

Official registry Developer tools

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

Source code Website Documentation

What can you do with Staats?

  • 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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http staats 'https://api.staats.ai/functions/v1/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "staats": {
            "type": "http",
            "url": "https://api.staats.ai/functions/v1/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Staats MCP Server
  2. Connect
  3. Tools
  4. Tracking
  5. Links

Staats MCP Server

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.

Frequently asked questions

What is Staats?

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

How do I install Staats?

It runs as a remote server. In Claude Code: claude mcp add --transport http staats 'https://api.staats.ai/functions/v1/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Staats need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Staats open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Staats?

It is published by MrViolets. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.