The Satsu MCP server

The MCP server lets Claude Code, Cursor, VS Code, Windsurf and other MCP clients read your Satsu numbers and take a few safe actions. It runs locally through the package and talks to the public API with your personal key.

The analytics tools return aggregated numbers only, never data about individual visitors. Sessions are derived from a daily-rotating fingerprint that cannot be linked across days; raw IP addresses and user agents are never written to the analytics database and pass through our message queue only until they are processed, at most 24 hours; no cookies, no persistent visitor IDs.

Setup

The easiest way: run init and answer yes to "Connect your coding agent?". Or sign in and add the server yourself.

npx satsu-analytics login

Add the server to your editor

The entry runs npx -y satsu-analytics mcp. The key is read from your user config, so the file is safe to commit and a teammate signs in on their own machine.

In .mcp.json in your project:

json

{
  "mcpServers": {
    "satsu": { "type": "stdio", "command": "npx", "args": ["-y", "satsu-analytics", "mcp"] }
  }
}

Any other MCP client takes the same command: npx -y satsu-analytics mcp.

Ask

Restart the editor, then try "How many visitors did my site have last week?".

Tools per plan

The MCP is on every plan. A tool your plan doesn't include answers "available on Pro" with an upgrade link instead of failing.

Tool	What it does	Plan
`list_sites`	Your sites with ID, name and domain	All
`traffic_summary`	Visitors and pageviews over a period (Free: within your plan's retention, 3 months)	All
`top_pages`, `top_sources`	Most viewed pages and top referrers	All
`breakdown`	One dimension at a time; pages and referrers on every plan, the rest on Pro	All / Pro
`goals`	Goals with IDs, names and rules	All
`ai_traffic`	Visits from AI assistants such as ChatGPT or Perplexity	Pro
`goal_conversions`	Conversions of one goal	Pro
`live_visitors`	Visitors on the site right now, as a count	Pro
`uptime_status`	Monitors with status and TLS state	Pro
`audit_results`	Latest result per audit pillar	Pro

Actions

Actions run immediately, within your plan limits and your own role in the workspace. A read-only member can read but not act. There are no deletes, archives or billing actions.

Everything an agent creates is marked "created by agent" in the site, goal and monitor lists, and each key lists its latest actions under API keys in the dashboard.

Tool	What it does	Plan
`create_site`	Create a site in a workspace	All
`set_site_domain`	Set the production domain; audits and monitors need it	All
`create_goal`	Create a `custom_event` or `path` goal	All
`update_goal`	Rename a goal or change its rule	All
`start_audit`	Start an audit now (the site needs a domain)	Pro
`create_monitor`	Create an uptime monitor	Pro

Revoke a key

Keys act as the user who created them. To cut an agent off, open API keys in the dashboard, find the key and revoke it. The next request from that machine fails until you run login again. logout only removes the key from your machine; revoke it in the dashboard to invalidate it.