Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CURSOR_API_KEY | Yes | Your Cursor Enterprise Admin API key. This key provides read access to team usage data and allows setting spending limits. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_team_members | List all team members with their roles and status. Returns name, email, role, and whether they've been removed. |
| get_spending | Get current billing cycle spending for all team members. Shows spend in dollars, included vs overage, fast premium requests, and spend limits. |
| get_daily_usage | Get daily usage data per user: lines added/deleted, applies, accepts, rejects, tabs, requests by mode (composer/chat/agent), models used, and client versions. |
| get_billing_groups | Get billing groups with member lists, group-level spend, and daily spend breakdown. Also returns billing cycle dates. |
| get_usage_events | 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. |
| set_spend_limit | 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. |
| get_dau | Get daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage. |
| get_model_usage | 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. |
| get_agent_edits | Get agent edit metrics: suggested vs accepted vs rejected diffs and lines. Shows how effectively the team is using AI-generated code. |
| get_tabs | Get tab autocomplete usage: suggestions shown vs accepted vs rejected, with line-level detail. |
| get_mcp_usage | Get MCP (Model Context Protocol) tool usage: which MCP servers and tools are being used, and how often. |
| get_file_extensions | Get top file extensions being edited with AI: which file types get the most AI suggestions, accepts, and rejects. |
| get_client_versions | Get Cursor client version distribution across the team: which versions are in use and what percentage of users are on each. |
| get_commands | Get command usage analytics: which Cursor commands are being used and how often. |
| get_plans | Get plan mode adoption: which models are being used in plan mode and how often. |
| get_team_overview | 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. |
| get_user_deep_dive | Deep dive into a specific user's usage: their spending, daily usage patterns, recent requests, and model preferences. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |