Skip to main content
Glama

Demo

Demo animation created with remotion-readme-kit


What This Does

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 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.

Related MCP server: Token Analyzer MCP

What's Included

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

Install

Cursor (Marketplace)

/add-plugin cursor-usage

Then set your API key in Cursor settings:

  • Open Settings → MCP

  • Find cursor-usage and set CURSOR_API_KEY to your Cursor Enterprise Admin API key

Claude Code

/plugin install cursor-usage

Manual (any MCP-compatible client)

Add to your MCP configuration:

{
  "mcpServers": {
    "cursor-usage": {
      "command": "npx",
      "args": ["-y", "cursor-usage-mcp"],
      "env": {
        "CURSOR_API_KEY": "your-api-key-here"
      }
    }
  }
}

As a Skill Only (no MCP server)

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.

Getting Your API Key

  1. Go to your Cursor team settings (Settings → Team → API Keys)

  2. Generate an Admin API key

  3. For analytics endpoints, you may also need an Analytics API key

The API key gives read access to your team's usage data. The only write operation is set_spend_limit.

Available Tools

Admin API

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

Analytics API

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

Composite Tools

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

Example Conversations

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..."

Full Cursor Enterprise Cost Monitoring Dashboard

This plugin answers quick questions in the IDE. For teams that need:

  • Historical trends over months (API is limited to 30 days)

  • Automated anomaly detection with statistical outlier detection

  • Slack/email alerts when spend spikes

  • Incident tracking with MTTD/MTTI/MTTR lifecycle

  • Web dashboard with charts and visualizations

See cursor-usage-tracker, the open-source Cursor Enterprise dashboard this plugin is part of.

Development

# 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 validate

Requirements

  • Node.js 20+

  • A Cursor Enterprise team with API access

  • Admin API key (and optionally Analytics API key)

Author

Ofer Shapira

LinkedIn GitHub

License

MIT © Ofer Shapira

Available Tools

17 tools
get_agent_editsB

Get agent edit metrics: suggested vs accepted vs rejected diffs and lines. Shows how effectively the team is using AI-generated code.

Inputs: startDate, endDate, users.

get_billing_groupsA

Get billing groups with member lists, group-level spend, and daily spend breakdown. Also returns billing cycle dates.

Inputs: no named parameters.

get_client_versionsA

Get Cursor client version distribution across the team: which versions are in use and what percentage of users are on each.

Inputs: startDate, endDate, users.

get_commandsC

Get command usage analytics: which Cursor commands are being used and how often.

Inputs: startDate, endDate, users.

get_daily_usageB

Get daily usage data per user: lines added/deleted, applies, accepts, rejects, tabs, requests by mode (composer/chat/agent), models used, and client versions.

Inputs: startDate, endDate, page, pageSize, +1 more.

get_dauB

Get daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage.

Inputs: startDate, endDate, users.

get_file_extensionsB

Get top file extensions being edited with AI: which file types get the most AI suggestions, accepts, and rejects.

Inputs: startDate, endDate, users.

get_mcp_usageB

Get MCP (Model Context Protocol) tool usage: which MCP servers and tools are being used, and how often.

Inputs: startDate, endDate, users.

get_model_usageA

Get model usage breakdown per day: which models are being used, how many messages, and by how many users. Essential for understanding model adoption and cost drivers.

Inputs: startDate, endDate, users.

get_plansB

Get plan mode adoption: which models are being used in plan mode and how often.

Inputs: startDate, endDate, users.

get_spendingB

Get current billing cycle spending for all team members. Shows spend in dollars, included vs overage, fast premium requests, and spend limits.

Inputs: page, allPages.

get_tabsB

Get tab autocomplete usage: suggestions shown vs accepted vs rejected, with line-level detail.

Inputs: startDate, endDate, users.

get_team_membersA

List all team members with their roles and status. Returns name, email, role, and whether they've been removed.

Inputs: no named parameters.

get_team_overviewA

Get a comprehensive team overview: member count, total spend, top spenders, DAU, and most-used models. This is the best starting point for understanding your team's Cursor usage.

Inputs: startDate, endDate.

get_usage_eventsA

Get granular per-request usage events with model, token counts, costs, and whether the request was chargeable. Supports filtering by user email and date range.

Inputs: email, startDate, endDate, page, +1 more.

get_user_deep_diveA

Deep dive into a specific user's usage: their spending, daily usage patterns, recent requests, and model preferences.

Inputs: email (required), startDate.

set_spend_limitA

Set a hard spending limit (in dollars) for a specific team member. Use with caution — this will block the user from making requests once the limit is reached.

Inputs: email (required), limitDollars (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific metrics or actions, such as get_agent_edits for edit metrics, get_daily_usage for user-level data, and set_spend_limit for administrative control. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_' prefix for retrieval operations and 'set_' for configuration, using snake_case throughout. This predictability enhances readability and usability for agents.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for the comprehensive analytics and management scope of Cursor usage. It covers various aspects like billing, usage, and team management without feeling overly bloated.

    Completeness5/5

    The tool set provides complete coverage for analytics and administrative tasks in the Cursor domain, including metrics retrieval (e.g., usage, spending, models), team management, and spend control. There are no obvious gaps, enabling agents to handle all relevant workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      Not graded
      maintenance
      Provides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.
      12
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides intelligent analysis of token usage patterns and optimization recommendations to improve efficiency and reduce costs in Claude Code sessions. Offers real-time analysis, cost metrics, and actionable insights for better context window and tool usage optimization.
      3 npm
      -
    • A
      license
      A
      quality
      C
      maintenance
      Real-time Claude.ai subscription awareness for AI coding assistants. Surfaces live utilization, forecasts limits, gates expensive operations, and measures real per-task cost.
      5
      16 npm
      6
      MIT