The acceptance rate is the metric worth having here — it says something about whether the tooling is landing, which raw request counts do not. Note that this reports on people: usage and spending are per named member, so treat it as the management report it is rather than a general analytics feed.
An MCP server over the Cursor team admin API. Three tools answer the three questions a team lead has: the roster, per-day usage metrics, and spending. It is read-only reporting, aimed at replacing a trip to the team dashboard with a question.
- `get_team_members` — everyone on the team with their name, email and role
- `get_daily_usage_data` — per-day metrics over a `startDate` and `endDate` in epoch milliseconds, returning lines added and deleted, AI suggestion acceptance rate, a breakdown of request types, the models used most, the extensions used most, and the client version
- `get_spending_data` — team spending per member with an optional `searchTerm`, sorting by field and direction, and `page` and `pageSize` for pagination
A Cursor team admin API key, supplied as `CURSOR_API_KEY` — it starts with `key_` and requires team admin rights. Node.js 16 or higher. The documented client entry names `cursor-admin-mcp`, which npm does not have; it puts the key in the `env` block and speaks stdio. The usage date range is capped: a request spanning more than 90 days is rejected, and dates must be epoch milliseconds with the end after the start.