Analytics for Claude Desktop Users: Query Your Site Data in Plain English

You’re already talking to Claude Desktop about your code, your docs, your writing. If you use Measure.events, you can now talk to it about your traffic too.

Measure.events ships an MCP server — the only analytics tool that does. And Claude Desktop supports MCP natively. That means you can ask your analytics questions the same way you ask Claude anything else: in plain English, right inside the app.

This post walks through how to set it up.

Why This Matters

Most analytics tools have dashboards. You open a browser, navigate to the tool, find the right date range, interpret the chart. It’s fine. But it’s a context switch.

Claude Desktop changes the pattern. If your analytics are connected via MCP, you can ask “what were my top pages last week?” or “where is my traffic coming from today?” without leaving the app. Claude fetches the data and tells you directly.

The MCP server isn’t a wrapper around the dashboard. It’s a first-class API interface — the same endpoints your code would call, exposed as tools Claude can invoke. You get structured data, not a screenshot.

Prerequisites

• Claude Desktop (macOS or Windows)
• A Measure.events account and API key
• About five minutes

Your API key is in your Measure.events dashboard under Settings → API Keys. It looks like mk_....

Setup: Edit claude_desktop_config.json

Open the Claude Desktop config file:

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

If the file doesn’t exist, create it.

Add the following configuration:

{
  "mcpServers": {
    "measure-events": {
      "url": "https://lets.measure.events/mcp",
      "headers": {
        "Authorization": "Bearer your_api_key_here"
      }
    }
  }
}

Replace your_api_key_here with your actual Measure.events API key.

Save the file, then fully quit and reopen Claude Desktop. The config is only read on startup.

Verify It’s Working

After restarting, you should see a small tool indicator in the Claude Desktop interface showing that the measure MCP server is connected.

Try asking:

“How many pageviews did my site get this week?”

Claude will call the Measure.events API, fetch your data, and respond with real numbers. If it works, you’re done.

What You Can Ask

With the MCP server connected, you have a conversational interface to all your Measure.events data:

Traffic overview:

• “What were my top 5 pages last week?”
• “How much traffic did I get today vs yesterday?”
• “Show me my pageview trend for the last 30 days”

Referrers:

• “Where is my traffic coming from this month?”
• “Is any traffic coming from social media?”
• “What’s my biggest organic traffic source?”

Site health:

• “Is my site getting any traffic right now?”
• “Which pages have the highest bounce rate?”
• “Which blog posts are performing best?”

Content decisions:

• “I published three posts last week — which one drove the most traffic?”
• “My homepage traffic dropped this week. What changed?”

Claude interprets the data and answers the question. You don’t need to write SQL or build a custom report.

Multiple Sites

If you track multiple sites with Measure.events, you can specify which one you want data from:

“What are the top pages on my blog site this week?” “Show me referrers for my SaaS app, not the marketing site”

The MCP server includes tools for listing all your sites, so Claude can discover them and reference them by name.

The Difference From a Dashboard

A dashboard shows you what it was designed to show. An MCP server answers what you actually want to know.

The dashboard is built for a generic user. Claude Desktop + MCP is built for your specific workflow. If you’re deep in a code session and want to know whether the landing page you just shipped is converting, you ask. You don’t alt-tab.

That’s the practical value. And since Measure.events is currently the only analytics tool shipping an MCP server, it’s not a feature you can get anywhere else.

Troubleshooting

Claude doesn’t see the MCP server: Make sure you fully quit Claude Desktop (not just close the window) and reopened it. The config is only read at startup.

“Tool not found” errors: Verify your API key is correct and your Measure.events account is active. The server will fail silently if the key is invalid.

npx isn’t available: If you don’t have Node.js installed, download it from nodejs.org. The npx command comes with it.

---

If you’re a Cursor user, we have a separate guide for Cursor MCP setup. The configuration is slightly different but the concept is identical.

Ready to connect your analytics? Sign up for Measure.events — free to start, no credit card required.