Connect an AI assistant (MCP)

Ask Claude, Cursor or any MCP client about your analytics in your own words. The assistant reads the same figures as your dashboard, with your own AI: SimpleData sends nothing to any AI company.

"How many visitors did I have this week, compared with last week?"
"Which pages bring the most visitors from Google this month?"
"Which channel did October's sales come from?"
"At which step of the purchase funnel do most people leave?"

What it is for

Your weekly review in a minute

"Sum up last week against the one before and tell me what changed most." The assistant reads the summary and the breakdowns and explains them.

Campaigns and launches

"How did the newsletter campaign do: visitors, sales and revenue?" It filters by UTM tags and reads the store figures.

Finding problems

"Which pages give the most 404s this month?", "Which pages lost the most visitors from Google?"

Sales and funnels

"Which channel brings the buyers who spend most?", "Where do people leave the checkout funnel, on mobile and on desktop?"

Next to your code

In Claude Code or Cursor, while you work on the site: "Did sign-ups change after Tuesday's deploy?"

Reports for clients

With one key per client site, "write October's report for this client" in your own words and format.

With other MCP servers

Your AI can combine SimpleData with the other servers you connect (your shop, your CRM, your notes) to answer questions that need both.

Before you start

The MCP server and the API are part of Pro.
Claude on the web and Claude Desktop connect by signing in with your SimpleData account: no key (below).
For any other client, create a key in Settings → API and MCP. Give it access to all your sites or to one. It is shown once: copy it then.
Keys and connections only read. Nothing can be changed or deleted with them. Up to 10 keys per account, 60 requests per minute each.
If the account goes back to Free, the keys stop working and are kept; they work again after upgrading.

Create a key →

Claude on the web and Claude Desktop, without a key

Add SimpleData as a custom connector. You sign in with your SimpleData account and Claude gets read-only access to all your sites. The connectors you add on claude.ai also appear in Claude Desktop.

In Claude: Settings → Connectors → Add custom connector.
Name: SimpleData. Remote MCP server URL:https://api.simpledata.dev/mcp
Press Add, then Connect. A SimpleData window opens: sign in if you are not (and enter your second-step code if you use one).
Check that it says Claude and press Allow Claude. Back in Claude, the connector shows as connected.
In a chat, turn SimpleData on in the tools menu and ask: "Which of my sites had the most visitors this week?"

You will see the connection in Settings → API and MCP → Connected apps, where you can disconnect it. Custom connectors are a Claude feature: whether your Claude plan includes them depends on Claude.

Other clients, with a key

Claude Code

In a terminal. Then type /mcp in Claude Code to check that simpledata is connected.

claude mcp add --transport http simpledata https://api.simpledata.dev/mcp \
  --header "Authorization: Bearer sd_..."

Cursor

In ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project). Do not commit a file that holds the key.

{
  "mcpServers": {
    "simpledata": {
      "url": "https://api.simpledata.dev/mcp",
      "headers": {
        "Authorization": "Bearer sd_..."
      }
    }
  }
}

VS Code (Copilot agent mode)

In .vscode/mcp.json. VS Code asks for the key the first time and keeps it encrypted, so the file can be committed.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "simpledata-key",
      "description": "SimpleData API key",
      "password": true
    }
  ],
  "servers": {
    "simpledata": {
      "type": "http",
      "url": "https://api.simpledata.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${input:simpledata-key}"
      }
    }
  }
}

Claude Desktop, with a key

If you prefer a key to signing in (for one site only, for example), Claude Desktop connects through mcp-remote (it needs Node.js). In Settings → Developer → Edit config.

{
  "mcpServers": {
    "simpledata": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.simpledata.dev/mcp",
        "--header",
        "Authorization:${SIMPLEDATA_AUTH}"
      ],
      "env": {
        "SIMPLEDATA_AUTH": "Bearer sd_..."
      }
    }
  }
}

Other clients

Any client that speaks MCP over HTTP (Streamable HTTP) and can send a header works: the address is https://api.simpledata.dev/mcp and the header is Authorization: Bearer followed by your key.

What the assistant can read

list_sites	Your sites, or the one the key is for.
get_summary	Pageviews, visitors, bounce rate, visit duration and top page; with the previous period if asked.
get_timeseries	Pageviews and visitors per hour, day, week or month.
get_breakdown	Top pages, entry and exit pages, referrers, channels, countries, devices, browsers, systems, UTM tags, outbound links, downloads and 404s.
get_realtime	Visitors in the last 5 minutes.
get_goals	Conversions of each goal.
get_goal_properties	A custom-event goal broken down by its properties.
get_ecommerce	Revenue, orders, average order, conversion, top products and revenue by channel.
get_payments	Each order with the source of the buyer's first visit. No customer data.
list_funnels, get_funnel	Your funnels and their results, step by step.
get_paths	The most frequent paths, added up.
get_ai_traffic	AI agents and crawlers that visit your site.
get_engagement	Scroll depth and time on page, for the site and its top pages.

Every figure is the one the dashboard shows for the same period and filters: visitors are the weekly anonymous identifier, a session is one visitor on one day, and there is nothing about individual people. Filters are the dashboard's too (is, is not, contains, does not contain and event properties, written as in the API's filter parameter), and days imported from another tool count unless a filter is on: get_summary says how many under imported.

Good to know

One key per device or tool, with a name you will recognise. If you lose a laptop or stop using a tool, revoke its key in Settings.
Disconnecting Claude in Settings stops it from renewing its access at once; the access it already has expires within an hour. Signing in only works for Claude and for apps that come back to your own computer; anything else needs a key.
Page paths, referrers, UTM tags and product names are written by whoever visits your site, and anyone can make them say anything. SimpleData tells the assistant to treat them as data and never as instructions, but be careful about letting the same assistant run commands or send messages without asking you while it reads them.
What the assistant reads is sent to the company that runs your AI, under your agreement with them: aggregated figures and orders without customer data.

If it does not connect

401 or "invalid_api_key": The key is wrong or was revoked, or the header is missing "Bearer " before the key.
403 or "pro_required": The account is on Free. The key works again after upgrading.
The client opens a browser to sign in: It did not send the key and offers to sign in instead. That is how Claude connects; for other clients, check that the header is in the configuration above.
"This app sends you back to…" and no Allow button: The app is not Claude and does not come back to your computer. Use a key with it.
The Allow button is missing and it mentions Pro: The MCP server is part of Pro, with a key or by signing in.
429 or "rate_limited": More than 60 requests in a minute with one key. Wait for the minute to end.

API reference: the same data from your own code

← Back to the docs