# Cursor Admin MCP for AI Agents MCP

> Cursor Admin MCP lets you manage your Cursor team through your AI agent. You can handle member access, audit logs, usage analytics, and spending limits without switching tabs. It connects to the Cursor Admin API to give you full oversight of your team's activity and costs from any MCP-compatible client.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_avg1IKfWXnVgRPbnb42ZvT82InRlFRjE0wtAZA3u/mcp
- **Tags:** team-admin, usage-tracking, audit-logs, spend-management, enterprise

## Description

Managing a team's AI tools usually means jumping between different dashboard tabs to check who has access, how much everyone is spending, and which repositories are being indexed. It is a lot of context switching that pulls you away from actual work. With this MCP, you can handle all those administrative tasks through a simple conversation with your AI client. Instead of hunting for a specific usage page or manually auditing logs to see who changed a setting, you just ask your agent to do it for you. You can pull up daily usage metrics to see which team members are the most active or set specific spending limits to keep your budget on track. It works by connecting your Cursor Admin API key to your workspace, making it a core part of your management toolkit. It is one of the many tools available in the Vinkius catalog that turns a complex back-office job into a series of quick commands. You get to stay in your flow while your agent handles the heavy lifting of team governance and cost attribution.

## Tools

### get_audit_logs
Retrieve admin events like billing changes or setting updates with filters for time and user.

### get_daily_usage_data
Pull per-user metrics for a specific date range to see daily activity levels.

### get_repo_blocklists
View the list of repositories currently blocked from AI indexing.

### get_spending_data
Get a breakdown of team spending including per-member costs for the current cycle.

### get_team_info
Fetch general team metadata like the team name and member count.

### get_team_settings
View the current configuration settings for your team.

### get_usage_events
Get granular data on model names and token usage for precise cost attribution.

### list_team_members
See every member on the team along with their specific roles and status.

### remove_team_member
Remove a user from the team using their email or unique user ID.

### set_user_spend_limit
Set or remove a dollar limit for a specific member to control their budget.

### update_team_settings
Modify specific fields in your team configuration using partial updates.

### upsert_repo_blocklists
Add new URLs or patterns to the repository blocklist or update existing ones.

## Prompt Examples

**Prompt:** 
```
Who are the admins on our team and what is their email?
```

**Response:** 
```
I've checked the team roster for you. Here are the current administrators:

| Name | Email | Role |
| :--- | :--- | :--- |
| **Alice Chen** | alice@company.com | Admin |
| **David Wilson** | david@company.com | Admin |

Would you like me to list the regular members as well?
```

**Prompt:** 
```
Show me the spending for the last 30 days.
```

**Response:** 
```
Here is the spending summary for the current billing cycle:

* **Alice Chen**: $45.20
* **Bob Smith**: $12.80
* **Carol Jones**: $87.50 (⚠️ Over limit)
* **David Wilson**: $33.10
* **Eve Brown**: $5.40

**Total Team Spend: $184.00**

Carol Jones has exceeded her $50 limit. Should I set a new limit for her?
```

**Prompt:** 
```
Are there any new repos on the blocklist?
```

**Response:** 
```
I've retrieved the current repository blocklist. Here are the active rules:

* `https://github.com/org/secret-repo` (Patterns: `*.env`, `secrets/*`)
* `https://github.com/org/private-data` (Patterns: `*`)

No other entries were found. Do you want to add a new repository to the blocklist?
```

## Capabilities

### Manage team members
Add or remove users from your organization by email or ID.

### Audit administrative actions
Review logs of team settings changes and billing events.

### Track daily usage
Get per-user metrics on lines added, tab completions, and chat requests.

### Control spending
Set individual spend limits and view detailed monthly breakdowns.

### Manage repo blocklists
Update which repositories are blocked from AI indexing.

### Update team configurations
Modify team settings and metadata via natural language.

## Use Cases

### Preventing Budget Overruns
A finance lead notices a spike in costs and asks the agent to find who exceeded their $50 limit and show their usage events.

### Rapid Offboarding
An admin needs to clear out old accounts and tells the agent to remove the user with a specific email from the team.

### Security Auditing
A security lead asks to see all changes to the repo blocklist from the last 48 hours to ensure no unauthorized access.

### Adoption Tracking
A manager asks for a summary of daily usage for the engineering team for the last week to measure ROI.

## Benefits

- Stop hunting through dashboards to find spending data. Use get_spending_data to see exactly who is using what and where the money goes.
- Keep your budget safe by setting hard limits. Use set_user_spend_limit to ensure no single user can blow your monthly budget.
- Audit your team's security posture easily. Use get_audit_logs to see every change made to settings or member roles.
- Protect your source code with ease. Use upsert_repo_blocklists to quickly block specific repositories from being indexed by the AI.
- Get clear visibility into team adoption. Use get_daily_usage_data to see which developers are actually using the tools every day.

## How It Works

The bottom line is you get a voice-controlled dashboard for your entire Cursor team's operations.

1. Subscribe to the MCP and generate a Cursor Admin API key with admin:* scope from your dashboard.
2. Paste your API key into your AI client's configuration settings.
3. Ask your agent to list members, check spending, or update blocklists.

## Frequently Asked Questions

**How do I get my Cursor Admin API key?**
Go to the Cursor Dashboard → Settings → API Keys to create an admin API key. The key starts with `crsr_` and must have the `admin:*` scope to access the Admin API. Copy the key and paste it into the API key field in the setup wizard. The key is sent as Basic Auth credentials (API key as the username, empty password) in every request to `https://api.cursor.com`.

**What API scope is required?**
The Admin API requires the `admin:*` scope on your API key. This scope grants access to team management, audit logs, usage data, spending controls, and team settings. Without the admin scope, API calls will return 401 Unauthorized. Generate your key from an admin account in the Cursor Dashboard.

**What are the rate limits?**
The Admin API has a rate limit of 20 requests per minute for most endpoints. The `set_user_spend_limit` endpoint has a higher limit of 250 requests per minute. If you exceed the rate limit, the API returns a 429 status code. The engine handles retries transparently where appropriate, but for bulk operations, consider spacing your requests.

**Can I manage team spending and set spend limits?**
Yes. Use `get_spending_data` to view per-member spending breakdowns including spendCents, overallSpendCents, fastPremiumRequests, and monthlyLimitDollars. Use `set_user_spend_limit` to set a monthly spend limit in dollars for any team member, or pass null to remove an existing limit. The spend limit endpoint has a higher rate limit of 250 requests per minute.

**Are audit logs available for security review?**
Yes. Use `get_audit_logs` to retrieve administrative audit events. You can filter by time range (startTime/endTime), event types (e.g. team_settings, member_management, billing), search text, and specific users. The response includes event types, timestamps, and descriptions of administrative actions. This is valuable for security reviews and compliance audits.

**Can I add and remove team members?**
You can remove team members using `remove_team_member`, which accepts either an email or a user ID. This is a destructive operation — the member loses access to the team immediately. To list current members and their roles, use `list_team_members`. Note that adding new members is typically done through the Cursor Dashboard invitation flow, not the Admin API.

**What usage data is returned?**
The `get_daily_usage_data` tool returns per-user daily metrics including lines added, lines deleted, tab completions, applies, accepts, rejects, and counts for composer, chat, and agent requests. The `get_usage_events` tool returns individual usage events with the model name, request kind, token usage, and the amount charged in cents. Together these provide a comprehensive view of how your team uses AI features.