Skip to main content
Cursor’s analytics API is only available on the Cursor Enterprise plan. You must be on Cursor Enterprise to connect this integration.

Benefits of Connecting Cursor to Windmill

Connecting Cursor to Windmill brings AI coding tool usage directly into stats, performance reviews, and 1:1s — giving managers and engineers visibility into how AI is being adopted across the team.
  • Tracks how engineers are using AI-assisted coding features like agent edits, tab completions, and chat
  • Surfaces adoption patterns across models, skills, and MCP tools without self-reporting
  • Helps managers understand AI tool usage and coach their teams on effective workflows
  • Provides concrete data for performance conversations about productivity and tool adoption
  • Syncs automatically — no manual tracking or surveys required
Windmill turns Cursor’s team analytics into actionable stats that flow into your existing performance workflow.

How to Connect Cursor

1

Get your API key from Cursor

Go to the Cursor Dashboard > Integrations page. Generate an API key for Windmill. You’ll need to be a Cursor team admin to access this page.
2

Open the Cursor integration in Windmill

In Windmill, navigate to Settings > Integrations, find Cursor, and click Connect.
3

Paste your API key and connect

Paste the API key from Cursor into the input field and click Connect. Windmill will validate the key and begin syncing analytics within the hour.
Cursor is an account-level integration — an admin connects it once and it covers your entire Cursor team. Individual users don’t need to connect separately.

Connected Data

When connected, Windmill syncs team-level analytics from Cursor’s API. This is aggregate usage data — Windmill does not access any code, files, or conversation content.
StatDescriptionUnit
Agent Edits AcceptedNumber of AI-generated code edits acceptededits
Agent Lines AddedLines of code added by Cursor’s AI agentlines
Agent Lines DeletedLines of code deleted by Cursor’s AI agentlines
Agent Edit Acceptance RateRatio of accepted to suggested AI edits%
Tab Completions AcceptedNumber of Cursor tab suggestions acceptedcompletions
Messages SentMessages sent to Cursor AI, broken down by modelmessages
Plan Mode MessagesMessages sent in Cursor’s plan mode, broken down by modelmessages
Ask Mode MessagesMessages sent in Cursor’s ask mode, broken down by modelmessages
Skill UsageCursor skill invocations, broken down by skillinvocations
MCP Tool UsageCursor MCP tool invocations, broken down by toolinvocations
All stats are tracked per employee, per day.

Visibility and Access

Cursor stats in Windmill follow the manager hierarchy visibility model:
  • Employees can see their own Cursor stats
  • Managers can see Cursor stats for their direct reports and anyone in their reporting chain
  • Admins can see Cursor stats for everyone in the organization
  • Peers cannot see each other’s Cursor stats
This means Cursor analytics are treated like other sensitive performance data in Windmill — visible to the people who need it for coaching and evaluation, but not exposed broadly.

Permissions

Windmill requests read-only access to Cursor’s analytics API.
PermissionPurpose
Read team analyticsTo sync usage stats per team member into Windmill
No access to code or filesWindmill never reads, stores, or accesses any code from Cursor
No access to conversationsWindmill does not read chat content — only aggregate usage counts
Read-only accessWindmill never modifies anything in Cursor

User Matching

Windmill matches Cursor users to employees using their email address. If a Cursor user’s email matches an employee’s email in Windmill, their stats are automatically attributed to that employee. If you notice stats that aren’t being attributed correctly, check that the email addresses in Cursor match the employee emails in Windmill.

FAQs

Yes. Cursor’s analytics API is only available on the Enterprise plan. The integration will not work with Cursor’s free, Pro, or Business plans.
No. Windmill only reads aggregate analytics data from Cursor’s API — usage counts, model breakdowns, and acceptance rates. Windmill never accesses code, files, repositories, or chat content.
Windmill syncs with Cursor once per hour. New usage data will appear within an hour of the activity happening in Cursor.
Yes. Every employee can see their own Cursor stats in Windmill.
No. Cursor stats follow the manager hierarchy — only your manager (and their managers) can see your stats. Peers cannot see each other’s Cursor usage data.
No. Cursor is an account-level integration. An admin connects it once using an API key from the Cursor dashboard, and it covers your entire Cursor team.
Their historical Cursor stats remain for context, but Windmill stops attributing new activity once they are an Archived user.
This usually happens when your email in Cursor doesn’t match your email in Windmill. Make sure the email addresses match, or ask an admin to check the user mapping.