Cursor Teams plan: seat prices, usage, admin and team rules

Updated 9 min read

Cursor’s Teams plan is priced per seat, and each seat has a tier: Premium at $30 a user a month, Super at $100 or Ultra at $200, plus a $0 Free seat for people who manage Cursor without using it. Each paid seat gets its own weekly pool of usage for Cursor’s models. The team pays for Claude, GPT and Gemini separately, at API list price plus $0.25 per million tokens, from a shared prepaid balance. Teams adds SSO, team rules, a team marketplace and usage analytics.

The figures here come from Cursor’s pricing page and its Teams pricing docs, read on 16 October 2026. Prices are in US dollars, before tax. Some of the pages that rank for “cursor team” describe the older billing: Cursor’s own August 2025 post on request costs, and a Reddit thread about the $40 seat.

How much does Cursor Teams cost?

Seat Price Weekly usage of Cursor models Who Cursor suggests it for
Free $0 a user a month None from the team IT, security or finance admins who manage Cursor without using it
Premium $30 a user a month Premium pool Everyday coding agent users
Super $100 a user a month 3.75x Premium Daily agent users who need more usage
Ultra $200 a user a month 12.5x Premium Power users running several agents or Automations

The rules, from Cursor’s members and seats page:

  • One team can mix tiers, for example three Premium seats and one Super seat. Seat tier is separate from role, so an Admin can hold any tier.
  • The $8 Plus plan is not available for teams.
  • A member on a Free seat draws on their own personal plan, or on the small free allowance if they have none. Free seats are assigned by email invite or from the Seat menu, not by invite link.
  • Cursor bills per active paid seat. A member added mid-cycle is charged pro rata, an upgrade applies at once and charges the difference, and a downgrade applies at the end of the billing period.
  • Yearly billing saves 20%. You cannot move from yearly back to monthly mid-plan.
  • Self-serve plans are paid by card. Invoices, purchase orders and wire transfers are for Enterprise.

What happened to the $40 Cursor Teams seat?

Cursor now sells its plans as part of “The X Subscription”, one subscription that covers Grok, Cursor and X. Teams created before it keep their legacy seats: Standard at $40 a user a month and Premium at $120 with 5x the Standard allowance. Those seats have two monthly pools, one for Cursor’s models and one for third-party models, and on-demand usage that is on by default and billed in arrears.

A legacy team can keep adding seats and changing seat types without switching. Switching is optional and permanent; an owner or admin does it at cursor.com/unify/team. Cursor maps Standard to a Premium seat ($30) and the old Premium to a Super seat ($100). It says each new plan includes at least twice the coding usage with Cursor models of the legacy plan it replaces, but drops the included allowance for third-party models.

If your team leans on Claude or GPT inside Cursor, work out that spend before you switch. A legacy seat included some of it; on the new seats all of it comes from prepaid credit.

How does usage work on a Cursor team?

Each paid seat has its own weekly pool for Cursor’s models (Grok 4.7, Grok 4.6, Grok 4.5 and Composer 2.5), and the pool refreshes weekly. Seats do not share pools, and usage does not move between members. Pooled usage across a team is an Enterprise feature.

Everything else comes out of one prepaid balance that the whole team shares:

  • Third-party models, from the first request, at the model’s public API list price plus the Cursor Token Rate of $0.25 per million tokens (input, output and cached tokens).
  • Cursor’s models once a seat’s weekly pool runs out, at their token rates, with no Cursor Token Rate.
  • Requests made with a member’s own API key. On Teams and Enterprise these still carry the Cursor Token Rate, paid from the team’s balance.

Admins buy credit with one-time top-ups or turn on Auto Top-up. They set one monthly limit on additional usage for the whole team, a default limit for each member, and per-member overrides. Paid usage stops when the balance is empty or the team limit is reached, whichever comes first. At the limit it pauses until next month or until an admin raises it, even if prepaid credit remains.

What does Cursor Teams add over an individual plan?

From Cursor’s Teams pricing docs and its dashboard docs:

  • Central billing and administration, with usage stats in the dashboard and through the Admin API.
  • Usage analytics for the team.
  • Team rules that apply to every member’s Agent in every repository, and can be enforced so members cannot turn them off.
  • One team marketplace for internal rules, skills, plugins and shared MCP servers.
  • Code review with Bugbot, and Cloud Agents and Automations with shared team context. These also come with the Premium individual plan and above.
  • Privacy Mode enforced for the whole team, and custom Chat data retention.
  • SAML or OIDC single sign-on, after you verify your domain.
  • Cursor Router modes beyond Cost mode: Balance and Intelligence pick between Cursor’s and third-party models for each request. Individual plans have Cost mode only.
  • Cursor’s MSA and DPA instead of the online terms.

Cursor Teams vs Enterprise

Teams Enterprise
Price $30, $100 or $200 a seat a month Custom
Usage Weekly pool per seat Pooled across the team
Billing Card Invoice or purchase order
Team marketplaces 1 Unlimited
SSO Yes Yes
SCIM, audit logs, service accounts No Yes
Model, repository and MCP access controls No Yes
Auto-run, browser and network controls No Yes
Support Community and standard Priority, first human response in 8 hours for critical issues

Cursor recommends Teams for anyone happy to self-serve and Enterprise for teams that need priority support, pooled usage, invoicing, SCIM or advanced security controls. The table follows Cursor’s Enterprise comparison.

How do you set up a Cursor team?

New users start at cursor.com/team/new-team; existing users click “Upgrade to Teams” in their dashboard. You pick a team name and a billing cycle, then invite people. Cursor’s setup page has the steps.

There are four ways to add members: email invites, an invite link, SSO (people join when they sign in with their company email) and domain matching (anyone with a verified email domain can join without an invite). Invite links have a long expiry and work for anyone who has them, so Cursor advises revoking them regularly or using SSO or domain restrictions instead.

There are three roles:

  • Members use Cursor’s paid features and see their own usage, but not billing or the admin dashboard.
  • Admins also add and remove members, change roles, set up SSO, manage billing and spending, and see team analytics.
  • Unpaid Admins have the same admin rights without a paid seat or Cursor’s paid features.

A team must always have at least one Admin and one paid member. On a Teams plan, a Cursor account belongs to one team at a time. Cursor’s docs say a removed member who has used credits keeps their seat occupied until the end of the billing cycle.

What does a Cursor team share, and what stays with each person?

Shared across the team Stays with each person
Team rules from the dashboard The weekly usage pool on their seat
The team marketplace: rules, skills, plugins and Team MCP servers User rules and files in ~/.cursor/rules
Project rules and AGENTS.md, through the repository MCP servers in ~/.cursor/mcp.json
The prepaid balance and spending limits Their own sign-in to each MCP provider
Privacy Mode, when an admin enforces it Personal skills synced for their own Cloud Agents

Team rules are the dashboard’s way to give every member the same instructions. Our Cursor rules guide covers how they compare with project rules and the order Cursor applies them in.

Few teams keep their instructions in Cursor’s own format, at least in public. When we checked the 1,000 most-starred active GitHub repositories on 12 October 2026, 34 had Cursor rules of either kind, against 365 with AGENTS.md and 259 with CLAUDE.md. Cursor reads AGENTS.md too, so a team whose members also run Codex or Claude Code can put shared conventions there and keep .cursor/rules for guidance scoped to certain files. The AGENTS.md guide lists which agents read which file.

Admins can add Team MCP servers to the Default team marketplace, according to Cursor’s plugins docs. That makes a server available for teammates to install in the IDE, the CLI and the Agent Window, and it is already available to Cloud Agents. It does not install or enable the server for every developer, and each developer may still need to sign in to the provider.

Rules and the marketplace hand out instructions and tools. What one member’s Cursor works out during a task (why a migration was rolled back, which service owns a queue) stays in that chat unless someone writes it down where the next agent will look.

Give every member’s Cursor the same wiki

Dexio is a hosted, open source (AGPL-3.0) wiki that AI agents read and write over MCP. Cursor, Claude Code, Codex and your other agents search, read, write and link markdown pages in the same wiki, and people see what their agents know as a page graph. Every change is kept, with the agent and the person behind it.

Each member connects their own Cursor by merging this into ~/.cursor/mcp.json, with their own API key in place of dxk_.... The step is from Dexio’s agent instructions, which Cursor’s Agent can also follow to set itself up:

{
  "mcpServers": {
    "dexio": {
      "url": "https://app.dexio.wiki/mcp",
      "headers": { "Authorization": "Bearer dxk_..." }
    }
  }
}

The Cursor MCP guide covers checking the connection and a rule that tells Agent when to use the wiki. We have not tried adding Dexio as a Team MCP server in Cursor’s marketplace.

Dexio is free for one person, then $10 (Team) or $20 (Business) a member a month, and agents never count as members. If your team only uses Cursor and shares a handful of conventions, team rules and AGENTS.md cost nothing extra. A wiki is worth adding when the same knowledge has to reach Cursor and your other agents, and you want to see and correct what they wrote.

FAQ

How much is Cursor for a team of five?

Five Premium seats are $150 a month, billed monthly. Usage of third-party models such as Claude comes on top, from the team’s prepaid balance.

Can I use my own API key on Cursor Teams?

Yes. Requests with your own key are billed by your provider, and Cursor still charges its $0.25 per million token rate on them, from the team’s prepaid balance.

Do Cursor team members share usage?

Not on Teams. Each paid seat has its own weekly pool, and usage does not move between members. Pooled usage is part of Enterprise.

Sources

Ask a question

Ask anything about Dexio.

About
We reply by email.