get_team_membersLABSCO SUMMARY
Three questions, three calls.
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.
What it is
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.
What you get
get_team_members— everyone on the team with their name, email and roleget_daily_usage_data— per-day metrics over astartDateandendDatein 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 versionget_spending_data— team spending per member with an optionalsearchTerm, sorting by field and direction, andpageandpageSizefor pagination
Requirements
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 package is not on npm, so it runs from a built clone: the client launches dist/index.js with node over stdio, with the key in the env block. 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.
Setup effort
Build from source — git clone https://github.com/h3ro-dev/cursor-admin-mcp.git
USE CASES
01
Seeing where the AI budget went
Pull spending per member, sorted by amount, instead of reading the billing page.
02
Checking whether the tooling is being used
Read the per-day acceptance rates and request types over a recent window.
03
Getting the roster with roles
List everyone on the team and their role in one call.
3 tools
Listed in project docs. Your client may show a different list.
get_daily_usage_dataget_spending_dataBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- Node.js 16+
- CURSOR_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/h3ro-dev/cursor-admin-mcp.git
cd cursor-admin-mcp
npm install
npm run build
cp .env.example .envEdit .env and add your CURSOR_API_KEY
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"cursor-admin": {
"command": "node",
"args": [
"<YOUR_PATH_TO_CURSOR_ADMIN_MCP>/dist/index.js"
],
"env": {
"CURSOR_API_KEY": "<YOUR_CURSOR_API_KEY>"
}
}
}
}
