mcpField
S
Staats

Staats

VerifiedFeaturedRemote
staats.aiData & Analytics0Updated 8w ago

About Staats

Staats is a hosted, cookieless web analytics service for coding agents. Through MCP, agents can query traffic and funnels, compare activity around deployments, and surface errors or visitor friction.

Key features

  1. 01Cookieless site analytics
  2. 02Traffic, funnel, and journey queries
  3. 03Deployment annotations and comparisons
  4. 04Surface errors and visitor friction
  5. 05Store site context

Use cases

  1. 01Ask an agent about site traffic
  2. 02Measure changes around a deployment
  3. 03Find notable shifts and JavaScript errors
  4. 04Set up sites and retain site context

MCP support

The hosted remote MCP server provides analytics tools for querying, comparing, and annotating site activity. One connection can cover all sites on an account.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.staats.ai/functions/v1/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

14
ParameterTypeRequiredDescription
sitestringNothe site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.

Details

From the project README

Staats MCP Server

Listed on mcpservers.org

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.