An astronaut overseeing a futuristic data hub

Connect Cursor Admin to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run your entire Cursor organization through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 12 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 12 available through Cursor Admin.

  1. 01

    Get team info

    This capability retrieves your team's metadata and high-level overview information.

  2. 02

    Get team settings

    Use this to pull the current configuration settings for your team.

  3. 03

    List team members

    This capability lists every member in your organization along with their assigned roles.

  4. 04

    Set user spend limit

    Set or remove a specific dollar limit for a team member's spending.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through Cursor Admin.

  1. 05

    Upsert repo blocklists

    This capability adds new repository blocklist entries or updates existing ones using URL and pattern rules.

  2. 06

    Get audit logs

    Retrieve administrative audit events, which you can filter by time, event type, or user.

  3. 07

    Get daily usage data

    Pull per-user daily usage metrics for a specific date range.

  4. 08

    Get repo blocklists

    This capability returns the current configuration of repositories blocked from AI indexing.

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through Cursor Admin.

  1. 09

    Get spending data

    Get detailed team spending data including breakdowns for every member.

  2. 10

    Get usage events

    Retrieve specific usage events to analyze model names, token counts, and costs.

  3. 11

    Remove team member

    Use this to immediately revoke a team member's access to the organization.

  4. 12

    Update team settings

    This capability allows you to modify specific fields within your team's configuration.

Real work

What teams actually run

01

Budget Enforcement

Set a monthly limit for a specific developer to prevent unexpected overages.

02

Security Compliance

Block specific repositories from being indexed to protect sensitive data.

03

Audit Reviews

Quickly scan recent administrative changes to ensure all actions were authorized.

04

Usage Monitoring

Analyze daily token usage and request counts to plan for future seat requirements.

One connector, every AI

Cursor Admin works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Cursor Admin to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

972ms average. Fast in production.

Cursor Admin is checked daily against the live service.

Daily averagePeak 1165ms
Oct 3Today
Fastest day
789ms
Slowest day
1165ms
14-day trend
Slowing+27%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 12 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Cursor Admin, so you can see the experience inside your AI.

It does not authenticate your account with Cursor Admin. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Cursor Admin Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_avg1IKfWXnVgRPbnb42ZvT82InRlFRjE0wtAZA3u/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Cursor Admin capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "cursor-admin-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_avg1IKfWXnVgRPbnb42ZvT82InRlFRjE0wtAZA3u/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Cursor Admin in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Cursor Admin owners hand off.

This MCP is built for leaders who need to manage Cursor usage without constantly logging into the web dashboard.

  • 01

    Team Administrators

    They hand off member management and setting updates to the AI.

  • 02

    Engineering Managers

    They use the AI to monitor adoption and identify heavy users.

  • 03

    Finance Teams

    They use the AI to pull spending data and enforce budget limits.

  • 04

    Security Teams

    They use the AI to review audit logs and manage repository blocklists.

FAQ

Questions Cursor Admin owners ask.

  • 01

    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.

  • 02

    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.

  • 03

    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.

  • 04

    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.

  • 05

    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.

  • 06

    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.

  • 07

    What usage data is returned?

    The get_daily_usage_data capability 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 capability 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.

Connect Cursor Admin to Claude, Cursor, ChatGPT & more