Analytics for Cursor

Cursor is built for developers who think in code. Adding BetterMeter via MCP means your analytics live right next to your source files. Deploy a change, then ask Cursor's AI: "Did traffic spike after that deploy?" — no tab switching, no dashboard login.

Configure MCP in Cursor

Cursor supports MCP servers natively. Add BetterMeter to your project's .cursor/mcp.jsonfile and it's available in every Composer and Agent session.

{
  "mcpServers": {
    "bettermeter": {
      "command": "npx",
      "args": ["-y", "@bettermeter/cli@latest", "mcp"],
      "env": {
        "BETTERMETER_API_KEY": "bm_..."
      }
    }
  }
}

The deploy-measure loop

The fastest feedback loop for web developers: write code in Cursor, deploy, then ask the AI about the impact — all without leaving the editor. This collapses what used to be a multi-tool workflow into a single environment.

• 01 Push a new landing page or feature
• 02 Ask: "Compare today's traffic to yesterday's"
• 03 See which referrers drive new visitors to the page
• 04 Check if any new bot crawlers discovered the page
• 05 Iterate on the code based on real data

Works with Cursor Composer and Agent

In Composer mode, Cursor's AI can call BetterMeter tools mid-conversation to answer your analytics questions. In Agent mode, it can autonomously check metrics as part of a larger coding task — like verifying that a performance optimization actually reduced bounce rates.

Project-level or global config

Add MCP config at the project level (.cursor/mcp.json) to scope analytics to a specific site, or configure it globally in Cursor settings to access all your BetterMeter sites from any project. The API key determines which sites are accessible.