Analytics for Cursor

Live web analytics, answered from inside Cursor.

Connect Cursor to your live web analytics. Ask about funnel conversion, traffic sources, or revenue from chat — without leaving the editor.

Connect Cursor — free See setup docs

What Cursor can answer

“What's the conversion impact of the PR I just shipped?”
Runs traffic.compare on the 24 hours before and after the deploy timestamp. Returns pageview, bounce, and event-volume deltas with a note on whether the sample is large enough to be conclusive.
“Which pages have the worst bounce rate this week?”
Calls pages.engagement sorted by bounce rate. Returns the top 10 with the secondary metric (avg time on page) so you can tell loaded-but-not-engaging from loaded-and-left.
“Revenue by country last month, top 10.”
Runs revenue.sum grouped by country. Returns the breakdown ordered by total — useful right before a pricing or localization decision.
“Are there any active error groups on /signup?”
Calls errors.groups filtered to /signup paths. Returns active groups with the most recent stack trace and affected-user count.

Connect in three steps

1
Sign in to your Clamp dashboard
Free tier, no credit card. Create a project if you haven't yet.
2
Click "Install in Cursor" on the Connections page
One click. Cursor opens with the connection registered. No config files, no API keys to paste.
3
Approve the connection in Cursor
Confirm once. Cursor can now read your analytics — scoped to the project you picked, respecting your dashboard role.

Answer the analytics question without context-switching

Cursor's strength is staying in the editor — you don't want to break flow to open a dashboard tab. With Clamp connected, the answer to "what's bouncing off this page?" or "how did revenue land this week?" comes back in chat. The dashboard stays available for when you want a visual — but for the questions that come up while you're shipping, Cursor answers them in place.

FAQ

Does this work in Cursor's chat AND in @-mentions?

Yes to both. The MCP tools are available wherever Cursor's agent can reach for context.

Does this cost extra?

No. The MCP connection is included on every tier including Free. There's no per-query cap.

Can Cursor write event-schema.yaml for me?

Yes — Cursor can call events.observed_schema to see what's actually firing, diff against your local YAML, and write the missing definitions. Useful when the codebase has drifted from the schema.

What about PII?

Clamp rejects email-shaped strings server-side, IP addresses are discarded after country lookup, and the MCP returns aggregated metrics by default.

Use a different agent?

Working with another MCP-compliant client? The Clamp MCP works with anything that speaks the protocol — see setup docs.

Try this in Cursor

Free tier covers 100K events/month. No credit card.