Connecting Cursor to Stacktic

For: a Cursor team admin. Takes about 5 minutes.

What this integration does

Connecting Cursor lets Stacktic see everyone with access to your Cursor Team. It also shows each person's role: Admin, Member, or Unpaid Admin.

On a Cursor Enterprise plan, Stacktic can also remove someone from the team during an offboarding.
On Team or Business plans, Cursor doesn't allow automatic removal at all. Stacktic still shows you who has access. You remove people who leave from the Cursor dashboard yourself.

To connect, you create a password for apps that belongs to the whole team, not to the person who makes it. Cursor calls this a Team API key. It keeps working after that person leaves. Stacktic stores it encrypted and only uses it with your one Cursor Team.

Stacktic needs one value:

Value	What it is
Team API Key	A key you create in the Cursor dashboard. It covers your whole team.

Before you start

You need to be an admin on the Cursor Team you want to connect. Only an admin can create a Team API key.
Know which plan your team is on: Team, Business, or Enterprise. It decides whether automatic removal will be available later.
If you manage more than one Cursor Team, each one needs its own Stacktic connection and its own key. One key belongs to exactly one team.

Step 1: Create a Team API key in Cursor

Sign in to the Cursor dashboard as a team admin.
Go to Settings → Cursor Admin API Keys.
Create a new key and copy it somewhere safe.

Cursor can change its dashboard without notice. This article doesn't try to describe every click inside it. If the screen looks different from what you expect, follow Cursor's own Admin API docs. They're the current source of truth for where this lives.

It doesn't matter which admin creates the key. Cursor's documentation says the key belongs to the team. Every admin can see it, and changes to the creator's own account later don't affect it.

Step 2: Connect in Stacktic

In Stacktic, go to Tools → Cursor → Integration. Paste the key into Team API Key.

Click Connect. Stacktic checks the key by reading your team's member list. If it can't, it tells you the key is wrong.

Step 3: Turn on removal (Enterprise plans only)

Stacktic starts reading who has access as soon as you connect. Removing someone during an offboarding is a separate switch. It's off until you turn it on, because removal is destructive.

Cursor only accepts automatic removal requests on an Enterprise plan. If your team is on Team or Business and you turn this switch on anyway, Stacktic still tries. Cursor is expected to refuse (see Troubleshooting below). On those plans, expect to remove people who leave yourself, from the Cursor dashboard.

What you'll see

Cursor's API doesn't share a team name or an account owner. So the connected card shows only the hidden key. You won't see a "connected as ___" line like some other integrations have.

Once you're connected, everyone on your Cursor Team shows up with one of three roles. These use the same words as Cursor's dashboard:

Admin (Cursor calls this role owner)
Member
Unpaid Admin (Cursor calls this role free-owner). This is an admin seat you don't pay for. It's often used for IT or finance staff who don't need to use the product.

Cursor's Admin API doesn't report two things, so you won't see them:

Last activity. Cursor's member list has no last-sign-in or last-used date. That column stays empty for everyone.
Anyone using a personal Cursor Individual account. An employee can use Cursor on their own Free or Pro subscription without ever joining your Team. This connection has no way to see that. Think of this member list as everyone on the paid Team, not everyone at your company who uses Cursor.

Security notes

Owned by the team, not a person. The key belongs to the team, not to one admin. Someone leaving your team won't break the connection.
No expiry. Cursor Team API keys don't expire on their own. They work until someone revokes them. Replacing the key from time to time is up to you.
Stored encrypted. Stacktic keeps only the key, encrypted. It never shows it again in full. You'll only see the last 4 characters, to help you tell connections apart.
You can cut it off anytime. Delete the key from Settings → Cursor Admin API Keys in the Cursor dashboard and the connection stops working right away.
Removal only affects Cursor. If Stacktic removes someone, it only removes their Cursor seat and Team access. It never touches a personal Cursor Individual account they might also have.

Troubleshooting

Message in Stacktic	Likely cause & fix
"Cursor refused the request (HTTP 401)."	The key was deleted or revoked in the Cursor dashboard. Create a new key and reconnect.
"Cursor refused the request (HTTP 403)" while reading your roster	A Cursor Team API key has no separate read permissions. It works for the whole team or not at all. So in practice this means the same thing as the 401 case above. Create a new key and reconnect.
Offboarding removal fails: "Cursor refused to remove this person… requires a Cursor Enterprise plan…"	Your team is on Team or Business, where Cursor doesn't allow automatic removal. Or the removal would leave the team with no paid member or no admin, which Cursor also blocks. Remove the person in the Cursor dashboard directly.
Offboarding removal reports the person wasn't found on the team	They were already removed, or were never a member. Stacktic counts this as done. You don't need to do anything.
Removal says Cursor reported success, but the person still shows up on the team	Stacktic double-checks every removal by reading the team back. It won't mark a removal done just because Cursor said so. Check the Cursor dashboard directly. If the mismatch keeps happening, contact Stacktic.

Frequently asked questions

Does this work on the Team or Business plan? Reading who has access works on every plan. Automatic removal during an offboarding is Enterprise-only. On Team or Business, Stacktic shows you the member list and you remove people yourself in Cursor.

Will connecting change or remove anyone right away? No. Connecting only reads your team's member list. Removal happens only during an offboarding, and only after you turn on automatic removal.

What about people using Cursor on their own personal (Individual) account? They won't appear here. Cursor's Admin API only sees members of the paid Team you connected. It can't see a personal Free or Pro subscription.

Does removing someone from Cursor delete their account? No. It only removes their seat and access on your Team. Their personal Cursor account, and any personal subscription, stay as they were.

We manage more than one Cursor Team. Can one connection cover all of them? No. A Team API key belongs to exactly one team. Each Cursor Team you want to see needs its own key and its own Stacktic connection.