How do I get a Cursor Analytics API key?

Sign in to your Cursor Dashboard, navigate to Settings → API Keys, and generate a new API key. Ensure the key has the admin:* scope. Analytics API access requires it. The key format is crsr_xxx. Copy it immediately as it may not be shown again. Paste it into the API key field above to connect.

Is an Enterprise plan required to use the Analytics API?

Yes. The Cursor Analytics API is available exclusively to Enterprise teams. If your team is not on an Enterprise plan, API requests will return HTTP 403 Forbidden. Contact your Cursor account manager or upgrade to Enterprise to gain access.

What analytics metrics are available?

This MCP provides 12 analytics endpoints: agent edits (suggested/accepted/rejected diffs and lines), tab autocomplete usage (suggestions, accepts, rejects, lines), daily active users (with CLI, cloud agent, and bugbot breakdowns), client version distribution, AI model usage (messages and users per model per day), top 5 file extensions per day, MCP capability adoption, Cursor command adoption, plan mode adoption, skills adoption, ask mode adoption, and a team leaderboard with configurable sorting and pagination.

What date formats does the API support?

All analytics endpoints support the following date formats for startDate and endDate: relative shortcuts (7d, 30d, today, yesterday, now), ISO 8601 strings (e.g. 2026-07-10T00:00:00Z), calendar dates in YYYY-MM-DD format, and Unix timestamps. When omitted, startDate defaults to 7d and endDate defaults to today.

Can I filter analytics by specific users?

Yes. All analytics endpoints accept an optional users parameter with comma-separated email addresses or user IDs. When provided, the API returns metrics filtered to only those users. This is useful for tracking individual or subgroup performance, or comparing team members on the leaderboard.

What are the API rate limits?

The Cursor Analytics API enforces the following rate limits: 100 requests per minute at the team level for standard analytics endpoints, 50 requests per minute for by-user analytics, and 20 requests per minute for conversation insights endpoints. If you exceed these limits, the API returns HTTP 429 and the engine surfaces a clear message asking you to wait.

Does the API support caching with ETags?

Yes. The Cursor Analytics API supports ETag-based caching. When you make a request, the API may return an ETag header. On subsequent requests, sending If-None-Match with that ETag value will return HTTP 304 Not Modified if the data hasn't changed, saving bandwidth and reducing rate limit consumption. The engine handles standard HTTP responses transparently.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Cursor Analytics 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. Turn raw coding telemetry into conversational intelligence.

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.

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.

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

01
Get client versions
This capability shows the distribution of Cursor client versions currently running in your organization. It helps you track software updates.
02
Get commands adoption
Use this to see which Cursor commands are most popular among your developers. You can filter by date or specific users.
03
Get daily active users
Retrieve daily active user counts for your team. It breaks down activity by CLI, cloud agent, and Bugbot usage.
04
Get leaderboard
Access a ranked list of team members based on AI usage metrics. You can sort by lines accepted, messages, or tab accepts.

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through Cursor Analytics.

05
Get mcp adoption
Track which MCP capabilities and servers your team is actually using. It provides usage counts per capability and per day.
06
Get plans adoption
Monitor how often your team uses Plan Mode to structure code before writing it. It supports date and user filters.
07
Get tab usage
Get stats on tab autocomplete usage, including accepts and rejects. You can filter by date or user.
08
Get top file extensions
Identify the most common file types being worked on by looking at suggestion volume per day. It returns the top 5 extensions.

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through Cursor Analytics.

09
Get agent edits
Get detailed metrics on AI-suggested code edits, including acceptance and rejection rates. You can filter by date or specific user emails.
10
Get ask mode adoption
This capability tracks how often your team uses Ask Mode to query their codebase. It supports date ranges and specific user filtering.
11
Get model usage
See a breakdown of which AI models your team uses most frequently. You can filter by date or specific users.
12
Get skills adoption
This capability monitors the usage of specific Cursor skills across your team. It works with date range and user filters.

Real work

What teams actually run

Measuring AI ROI

An Engineering Manager asks for the last 30 days of edit acceptance rates to justify AI capability spend.

Feature Rollout Tracking

A Team Lead checks Plan Mode adoption to see if the team is actually using the new planning workflow.

Tooling Audit

A Platform Engineer queries MCP adoption to see which external capabilities are most integrated into the workflow.

Cost Optimization

A DevOps lead checks model usage breakdown to understand which models are driving the most volume.

One connector, every AI

Cursor Analytics 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 Analytics 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

961ms average. Fast in production.

Cursor Analytics is checked daily against the live service.

Daily averagePeak 1245ms

Oct 6Today

Fastest day: 732ms
Slowest day: 1245ms
14-day trend: Improving-17%

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 Analytics, so you can see the experience inside your AI.

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

Cursor Analytics Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Cursor Analytics capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "cursor-analytics-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_H9OWwxFXSPPU6eyXPduRCKXQ8tGqPSGu6oKasFrL/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 Analytics in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Cursor Analytics owners hand off.

This MCP is designed for engineering leadership and platform teams who need to quantify AI impact.

01
Engineering Managers
They use the agent to measure AI adoption and ROI across the entire engineering org.
02
Team Leads
They check leaderboards and usage stats to see which features drive the most productivity.
03
Platform Teams
They monitor client versions and MCP capability adoption to plan rollouts and updates.

FAQ

Questions Cursor Analytics owners ask.

01
How do I get a Cursor Analytics API key?
Sign in to your Cursor Dashboard, navigate to Settings → API Keys, and generate a new API key. Ensure the key has the admin:* scope. Analytics API access requires it. The key format is crsr_xxx. Copy it immediately as it may not be shown again. Paste it into the API key field above to connect.
02
Is an Enterprise plan required to use the Analytics API?
Yes. The Cursor Analytics API is available exclusively to Enterprise teams. If your team is not on an Enterprise plan, API requests will return HTTP 403 Forbidden. Contact your Cursor account manager or upgrade to Enterprise to gain access.
03
What analytics metrics are available?
This MCP provides 12 analytics endpoints: agent edits (suggested/accepted/rejected diffs and lines), tab autocomplete usage (suggestions, accepts, rejects, lines), daily active users (with CLI, cloud agent, and bugbot breakdowns), client version distribution, AI model usage (messages and users per model per day), top 5 file extensions per day, MCP capability adoption, Cursor command adoption, plan mode adoption, skills adoption, ask mode adoption, and a team leaderboard with configurable sorting and pagination.
04
What date formats does the API support?
All analytics endpoints support the following date formats for startDate and endDate: relative shortcuts (7d, 30d, today, yesterday, now), ISO 8601 strings (e.g. 2026-07-10T00:00:00Z), calendar dates in YYYY-MM-DD format, and Unix timestamps. When omitted, startDate defaults to 7d and endDate defaults to today.
05
Can I filter analytics by specific users?
Yes. All analytics endpoints accept an optional users parameter with comma-separated email addresses or user IDs. When provided, the API returns metrics filtered to only those users. This is useful for tracking individual or subgroup performance, or comparing team members on the leaderboard.
06
What are the API rate limits?
The Cursor Analytics API enforces the following rate limits: 100 requests per minute at the team level for standard analytics endpoints, 50 requests per minute for by-user analytics, and 20 requests per minute for conversation insights endpoints. If you exceed these limits, the API returns HTTP 429 and the engine surfaces a clear message asking you to wait.
07
Does the API support caching with ETags?
Yes. The Cursor Analytics API supports ETag-based caching. When you make a request, the API may return an ETag header. On subsequent requests, sending If-None-Match with that ETag value will return HTTP 304 Not Modified if the data hasn't changed, saving bandwidth and reducing rate limit consumption. The engine handles standard HTTP responses transparently.

Explore

More in Developer Tools

Connect Cursor Analytics to Claude, Cursor, ChatGPT & more

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

Each Connector runs inside its own sealed environment.

One switch stops every agent. Instantly.

Spending limits that pause instead of surprise.

We ship only the actions that matter.

01-04

Get client versions

Get commands adoption

Get daily active users

Get leaderboard

05-08

Get mcp adoption

Get plans adoption

Get tab usage

Get top file extensions

09-12

Get agent edits

Get ask mode adoption

Get model usage

Get skills adoption

What teams actually run

Measuring AI ROI

Feature Rollout Tracking

Tooling Audit

Cost Optimization

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

Cursor Analytics Connector

Claude Desktop

Engineering Managers

Team Leads

Platform Teams

How do I get a Cursor Analytics API key?

Is an Enterprise plan required to use the Analytics API?

What analytics metrics are available?

What date formats does the API support?

Can I filter analytics by specific users?

What are the API rate limits?

Does the API support caching with ETags?

Cursor Admin AI Connector

Enterprise User Adoption Analytics AI Connector

CodeRabbit AI Connector

Builder Team Velocity Metrics AI Connector

Suggestions

Adobe Analytics AI Connector

AI Feature Usage Analytics AI Connector

Enterprise Demo Conversion Analytics AI Connector

Code Climate AI Connector