Metermark for Cursor
Cursor usage dashboard and metrics for engineering leaders
Cursor’s dashboard tells you who used it. Metermark puts that beside every other AI tool you pay for, so you can see what the seat budget is worth. Not a word of the conversation stored.
You can see Cursor activity. Not whether the seat budget is working.
Cursor’s admin view shows seats, requests, accepted suggestions and the model each person used. It is a good record of activity. What it can’t tell you is whether the money is buying anything: the Cursor bill lands next to Claude Code, GitHub Copilot and an API invoice, and nothing joins them.
The question an engineering leader gets asked isn’t “how many requests did we make”. It’s “is this worth it, and who should get more of it”. Answering that needs the cost of every tool, the work that came out, and the people behind both, in one place.
What Cursor’s admin dashboard and Team Analytics already cover
Cursor gives Team and Enterprise admins a real analytics surface, and you should use it.
- Team Analytics: active users, requests, lines of code suggested and accepted, and tab completions per person over time.
- The Analytics API on Enterprise: the same numbers as data, for your own warehouse or spreadsheet.
- Conversation Insights on Enterprise: what people are working on inside Cursor, from Cursor’s side of the conversation.
- Model and spend controls: which models a team may use, and what the usage-based part of the bill looks like.
What engineering leaders still can’t answer from Cursor alone
- What the whole AI bill buys. Cursor reports Cursor. The same engineer’s Claude Code sessions, Copilot licence and Bedrock calls are three other dashboards.
- Cost per outcome. Requests and accepted lines are activity. Whether a project shipped, and what the AI time on it cost, is a different number, and it is the one a retro needs.
- Who gets the most from it, and what they do differently. Per-user activity says who is busy. It doesn’t say whose habits are worth writing into the rules file everyone else reads.
- Whether to move budget between tools. A seat cut in one place and a bump in another needs both tools measured the same way.
How Metermark fits: a measurement layer, not a Cursor replacement
Metermark reads what each vendor exposes and lays the results side by side. For Cursor that is cost, model and user: the Metermark agent picks up Cursor sessions on each machine alongside Claude Code and Codex, and a Cursor Business admin key adds organization-level usage. Cursor shows less of the work than some tools do, and Metermark labels it that way rather than guessing.
For tools that do show the work, such as Claude Code, Metermark also labels the kind of work on the machine and counts what came out of it in commits and lines changed. Either way, not a word of the conversation is stored: the prompt is labelled locally and thrown away, and the model’s reply is never opened.
You keep Cursor’s admin dashboard for Cursor questions. Metermark answers the cross-tool ones: what every AI tool cost, what came out of it, who’s best at it, and where the AI time on a project went. A read-only API and an MCP server expose every number, so the answer lands in a spreadsheet, a board deck or a chat rather than another dashboard.
Plugs into
- Claude Code
- Cursor
- GitHub Copilot
- ChatGPT Enterprise
- Claude.ai
- Codex CLI
- Gemini CLI
- AWS Bedrock
- Google Vertex
- Azure OpenAI
- Windsurf
- Devin
Who this page is for
Three people who get asked what the Cursor seats are worth.
The engineering leader who signs the Cursor renewal
You want the seat count and the bill defended with something better than “people seem to like it”.
The platform or DevEx team rolling out more than one tool
Cursor for some, Claude Code for others, Copilot by default. You need one way to measure all three.
Finance asking what AI costs per team
One number across tools, split by team, project and kind of work, straight from the server rather than a slide.
Not for reading anyone’s Cursor conversations. Nobody reads the conversation. Not us, not your boss. Details in the privacy policy.
FAQ
The questions a Cursor admin asks first.
Does Cursor have a usage dashboard?
Yes. Cursor Team and Enterprise admins get Team Analytics: active users, requests, lines of code suggested and accepted, and tab completions per person over time. Enterprise adds an Analytics API. It reports Cursor only; Metermark puts those numbers beside the other AI tools you pay for.
Does Metermark replace Cursor’s Team Analytics?
No. Cursor’s dashboard is the best view of Cursor activity on its own, and you should keep using it. Metermark is the layer that puts Cursor’s cost and usage beside every other AI tool you pay for and asks what the spend is worth.
What does Metermark see from Cursor?
Cost, model and user: what Cursor exposes. Cursor shows less of the work than Claude Code does, so Metermark labels Cursor as cost and activity rather than claiming to know the kind of work done in it. Tools that show the work get the fuller picture.
Does Metermark store Cursor conversations?
No. Not a word of the conversation stored. Where a tool exposes prompts, they are labelled on the machine and deleted; the model’s reply is never opened. One row per session leaves the machine.
How does Metermark get Cursor data?
One command installs the Metermark agent on each machine, or IT pushes a signed package to the fleet with Jamf, Kandji or Intune. It reads the history the tools on that machine already keep and sends a row per session, not the content. A Cursor Business admin key adds organization-level usage.
Which other AI tools does Metermark cover?
Claude Code, Cursor, GitHub Copilot, ChatGPT Enterprise, Claude.ai, Codex CLI, Gemini CLI, AWS Bedrock, Google Vertex, Azure OpenAI, Windsurf and Devin, each labelled by how much the vendor exposes.
How much does Metermark cost?
Free for one person, with no card and no contract. Teams pay per seat; the current price is in the pricing section of the home page.
See your own numbers today.
One command. Free for one person. No card, no contract.
Start freeLook at the demo first
Rolling out to a team? Start with yourself, then invite them from the dashboard.