Your analytics, inside Cursor

Connect with one prompt

Open Connect agent in your dashboard, click Copy setup prompt, and paste it into your coding agent. It installs tracking for your framework and verifies MCP access with a real analytics query. No StepMetrics npm package is required.

{
  "mcpServers": {
    "stepmetrics": {
      "url": "https://app.stepmetrics.co/mcp",
      "headers": { "Authorization": "Bearer dak_..." }
    }
  }
}

What you can ask

• Which pages lost traffic compared with last week, and where that traffic came from.
• Where mobile visitors from a given source drop out of the signup funnel.
• Whether Tuesday's spike was people or a crawler, and what was filtered.
• How this month compares with last month, and with the same month last year.
• Which of your own agents cost the most this week, and which model that was.

Twenty-eight read-only tools sit behind those questions: sites, overview, live visitors, series, top pages and sources, returning visitors, each visitor and their visits, breakdowns, conversions, funnels, event checks, the ignore list, the All sites dashboard layout, clickstream on Pro and Scale, and five over agent telemetry. The agent calls the same query functions the dashboard calls, so the two cannot disagree about a number.

What it cannot do

Nothing writes. There is no tool that creates, deletes or mints anything, and the key it takes is read scope. A site id from another account returns the same "not found" as a site that does not exist. "The model would not do that" is not a security control, so the endpoint is built so that it cannot.