AI & Data

Connect Cursor

Reads Cursor Admin API per-member usage (active users, seats, tab suggestions/acceptances over a 28-day window) so AI ROI Adoption is measured from connected data rather than a typed percentage.

What you'll need

A Cursor team Admin API key (cursor.com/dashboard → API Keys). Team-admin only; Enterprise Admin API. The connector only issues read requests (members + daily usage).

Credential

Team Admin API key (read-only usage)

Requested scopes

Admin API: team members (read), Admin API: daily usage data (read)

Powers

AI ROI (adoption)

What it pulls

Team members (seat count) and per-member daily usage (active users, tab suggestions and acceptances) over a trailing 28-day window, persisted as ai_tool_usage.

What you’ll enter

The exact fields the connect form asks for — and where to find each value.

Admin API key: cursor.com/dashboard → API Keys → New API Key (team admin). Copy it now — shown once. The connector only reads team members and per-member usage.

Step-by-step setup

1
Open API Keys
Go to cursor.com/dashboard → API Keys (team admin). Only a team admin on a plan that includes the Admin API can create a key.
2
Create an Admin API key
Click New API Key, name it “ShipReady Metrics”, and copy the Admin API key immediately — Cursor shows it once (key_… or crsr_…). The key reads members and usage only.
3
Paste it above
The connector reads team members and per-member daily usage only. It never writes settings, spend limits, or code.
4
Connect
Click Connect Cursor. We validate the key against /teams/members, encrypt it at rest, and pull 28-day usage.

Create a Cursor Admin API key → Connect in the app

Built · awaiting live verification

Mocked-fetch tested against the Cursor Admin API members + daily-usage-data shape; no live team has connected.

Read-only Admin API adapter, mocked-fetch tested against the documented members + daily-usage-data shape. Awaiting a live org run before the Works-with strip names it.