Cursor Usage Plugin — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Cursor Usage Plugin (MCP Server) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<p align="center"> <img src="assets/logo.svg" alt="Cursor Usage - MCP server plugin for Cursor Enterprise API spending and analytics" width="100" height="100" /> </p>
<h1 align="center">Cursor Usage - Enterprise AI Spend Tracking Plugin</h1>
<p align="center"> An MCP server plugin that wraps the Cursor Enterprise API. Ask your AI agent about your team's spending, usage, and model adoption. Get answers in seconds, not spreadsheets. </p>
<p align="center"> <a href="https://github.com/ofershap/cursor-usage/actions/workflows/ci.yml"><img src="https://github.com/ofershap/cursor-usage/actions/workflows/ci.yml/badge.svg" alt="CI" /></a> <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT" /></a> <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-strict-blue" alt="TypeScript" /></a> <a href="https://modelcontextprotocol.io"><img src="https://img.shields.io/badge/MCP-compatible-green" alt="MCP" /></a> <a href="https://www.npmjs.com/package/cursor-usage-mcp"><img src="https://img.shields.io/npm/v/cursor-usage-mcp" alt="npm" /></a> <a href="https://github.com/ofershap/cursor-usage-tracker"><img src="https://img.shields.io/badge/dashboard-cursor--usage--tracker-blue" alt="Dashboard" /></a> </p>
Demo
<sub>Demo animation created with <a href="https://github.com/ofershap/remotion-readme-kit">remotion-readme-kit</a></sub>
You manage a Cursor Enterprise team. You want to know who's spending what, which models are being used, and whether you're getting value from AI. Instead of logging into a dashboard, you ask your AI agent:
"How much did my team spend this week?"
"Who's using the most expensive models?"
"Give me a full usage report for the current billing cycle."
This MCP server plugin wraps the full Cursor Enterprise Admin and Analytics APIs, giving your agent the tools and knowledge to answer those questions directly. Works with Cursor, Claude Code, and any MCP-compatible client.
Part of the [cursor-usage-tracker](https://github.com/ofershap/cursor-usage-tracker) ecosystem. This plugin handles quick questions in the IDE. The tracker is the full open-source dashboard with charts, three-layer anomaly detection, Slack/email alerts, and incident lifecycle tracking. Use them together or separately.
| Component | What it does |
|---|---|
| MCP Server | 15 tools wrapping the full Cursor Enterprise Admin + Analytics API |
| Skills | Data interpretation guide + cost optimization framework |
| Rules | Always-on cost-awareness guidance for model selection |
| Commands | Quick-access: /usage-report, /spend-check, /model-audit |
| Agent | Specialized usage analyst persona |
/add-plugin cursor-usageThen set your API key in Cursor settings:
cursor-usage and set CURSOR_API_KEY to your Cursor Enterprise Admin API key/plugin install cursor-usageAdd to your MCP configuration:
{
"mcpServers": {
"cursor-usage": {
"command": "npx",
"args": ["-y", "cursor-usage-mcp"],
"env": {
"CURSOR_API_KEY": "your-api-key-here"
}
}
}
}Copy the skills/ directory into your project's .cursor/skills/ or .claude/skills/ folder. The skills work standalone as reference material even without the MCP server.
The API key gives read access to your team's usage data. The only write operation is set_spend_limit.
| Tool | Description |
|---|---|
get_team_members | List all team members with roles and status |
get_spending | Current billing cycle spend per member |
get_daily_usage | Daily usage data: lines, requests, models, modes |
get_billing_groups | Billing groups with member lists and spend |
get_usage_events | Per-request events with model, tokens, and costs |
set_spend_limit | Set a hard spending limit for a user |
| Tool | Description |
|---|---|
get_dau | Daily active users (includes CLI, cloud agent, Bugbot) |
get_model_usage | Model usage breakdown per day |
get_agent_edits | Agent edit acceptance/rejection rates |
get_tabs | Tab autocomplete effectiveness |
get_mcp_usage | MCP tool adoption |
get_file_extensions | Top file types being edited with AI |
get_client_versions | Cursor version distribution |
get_commands | Command usage analytics |
get_plans | Plan mode adoption |
| Tool | Description |
|---|---|
get_team_overview | One-call summary: members, spend, DAU, top models |
get_user_deep_dive | Deep dive into a specific user's usage patterns |
Quick spend check:
You: "How much has my team spent this billing cycle?" Agent: _calls get_team_overview_ → "Your team of 47 active members has spent $3,842 this cycle. Top spender is Alice at $412, followed by Bob at $287..."
User investigation:
You: "Why is Bob's spend so high?" Agent: _calls get_user_deep_dive_ → "Bob has made 847 requests this week, 73% using claude-opus-4.5. His daily average is $41 vs the team median of $12. Switching his chat requests to Sonnet would save approximately $180/month..."
Model audit:
You: "/model-audit" Agent: _calls get_model_usage + get_spending + get_agent_edits_ → "62% of your team's messages use Sonnet (good). However, 5 users account for 78% of all Opus usage. Their acceptance rate on Opus is 44% vs 51% on Sonnet, suggesting Opus isn't providing measurably better results for most of their tasks..."
This plugin answers quick questions in the IDE. For teams that need:
See [cursor-usage-tracker](https://github.com/ofershap/cursor-usage-tracker), the open-source Cursor Enterprise dashboard this plugin is part of.
# Install dependencies
npm install
# Run in development
npm run dev
# Build
npm run build
# Type check
npm run typecheck
# Run tests
npm test
# Validate plugin structure
npm run validateOfer Shapira
MIT © Ofer Shapira
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.