What does a control plane for Cursor do?

It sits between Cursor and every system it touches, so the whole organization runs through one governed path. From a single platform you connect tools, provision access by team, control spend, and secure every interaction. Cursor usage scales without trading speed for safety.

How does Speakeasy connect Cursor to enterprise systems?

Speakeasy provisions MCP servers for every tool and system Cursor needs to reach. Pre-built connectors cover common SaaS like GitHub, Linear, and Sentry. Internal APIs become managed MCP servers from an API definition. Everything goes through one governed path.

How does Cursor authenticate to internal systems?

Through your existing identity provider. Speakeasy plugs into Okta, Microsoft Entra ID, Auth0, WorkOS, Google Workspace, or any SAML or OIDC provider. Cursor inherits the user's existing roles and permissions, so no new account model is created and access stays consistent with what the user already has.

Can I scope which tools each team or person can access?

Yes. Provision sub-catalogs per team so each group of engineers sees only the MCP servers and toolsets relevant to their work. Permissions can scope down to the individual tool, and credential management replaces the pattern of developers pasting API keys into Cursor.

How is data exfiltration prevented?

Every prompt and response is inspected in real time. Source code, PII, and exfiltration patterns are actively blocked. Prompt injection and shadow MCPs are passively detected. Alerts integrate with your existing SIEM, and a full audit trail records who asked what, when, against which data.

Does this change how developers use Cursor?

No. Speakeasy layers onto Cursor without changing the editor. Developers keep using Cursor the way they already do; the control plane sits behind the scenes managing connections, identity, and policy.

What is the rollout pattern most companies follow?

Pick one team and one set of tools (often a platform team with GitHub and Linear), route them through Speakeasy, prove value, then expand. Per-team registries make it easy to roll out to one team at a time without blocking the rest of the organization.

How does Speakeasy control Cursor costs?

Token use is attributed to a team, user, and tool, so spend is never a black box. Set monthly budgets per team and enforce them in real time, with alerts as a team approaches its limit and a hard cap when it hits it. Leadership sees spend trending before the invoice arrives, and chargebacks hold up because every cost traces back to who incurred it.

Your control planeforCursor

Connect tools, provision access by team, control spend, and secure every interaction. One platform to govern Cursor across your engineering org.

Talk to us

hero.tsx — marketing-site

Explorer▸ srchero.tsxhero-animation.tsxpage.tsxdata.ts

hero.tsxdata.ts

1export function Hero() {

2 return (

3 <section className="hero">

4 <h1>Control plane</h1>

5 </section>

6 )

Chat

Auto

Add a pricing section

Updated the hero and wired the CTA.

hero.tsx+24 -3

Apply

Ask anything

speakeasy

Connect

ServersToolsAgents

Secure

PoliciesSecrets

Costs

EmployeesAgents

Observe

SessionsLogs

Speakeasy / Default

Servers36

Tool calls4.4K

Spend$987

Sessions489

Top serversView all

github

slack

notion

Top agentsView all

1cursor

claude-code

codex

Employee activityLive

hector

Release checklist

8s ago

sagar

Auth refactor

22s ago

katrina

Pricing copy

1m ago

The problem

Cursor adoption is outpacing engineering control

Engineers adopt Cursor faster than the org can roll it out, see how it gets used, or keep its costs in check.

No centralized rollout

Developers install Cursor and configure their own MCP servers and keys. There's no central place to approve tools or give every engineer the same vetted setup.

No usage oversight

Once Cursor is connected, there's no shared view of which repos, APIs, and data it reaches, what actions it runs, or who is running them.

No cost controls

Token spend climbs across teams with no budgets or limits. Costs surface on the invoice, long after the usage that drove them.

The solution

Build your control plane for Cursor

Speakeasy sits between Cursor and every system it touches. Connect tools, provision access by team, control spend, and secure every interaction from one platform.

Connect

Internal APIs, SaaS tools, and databases reach Cursor through one governed path. No custom integration work per tool.

Provision

Enterprise OAuth, role-based permissions, and per-team registries. Control who reaches which tools, down to the individual.

Cost

Attribute every token to a team, set budgets, and cap runaway usage before it lands on the bill.

Secure

Inspect every prompt, response, and tool call in real time. Block code and secrets from leaving and catch threats in flight.

Connect

Connect Cursor to everything, safely

Internal APIs, SaaS tools, and databases reach Cursor through a single governed path. Every connection is credentialed, scoped, and audited before Cursor touches a system. No custom integration work per tool.

Your APIs

Your SaaS

Your data

NameVisibilityTools

Slack

Private

24 TOOLS

GitHub

Private

32 TOOLS

Notion

Private

18 TOOLS

Linear

Public

20 TOOLS

internal-billing-api

Private

12 TOOLS

user-service

Private

9 TOOLS

Snowflake

Disabled

NO TOOLS

inventory-api

Private

6 TOOLS

SaaS catalog

Browse a growing catalog of pre-built MCP servers for tools like GitHub, Linear, and Sentry. Deploy in one click.

Internal APIs

Turn any internal API into an MCP server by pointing at your API definition. Cursor reaches your proprietary systems in minutes.

Secure by default

Credentials stay vaulted and are never exposed to the model. Every tool call runs through policy checks and lands in an audit log.

Token-efficient

Curate tools into focused toolsets and utilize code mode to reduce token usage and improve agent accuracy.

Connect

Connect Cursor to everything, safely

Your APIs

Your SaaS

Your data

NameVisibilityTools

Slack

Private

24 TOOLS

GitHub

Private

32 TOOLS

Notion

Private

18 TOOLS

Linear

Public

20 TOOLS

internal-billing-api

Private

12 TOOLS

user-service

Private

9 TOOLS

Snowflake

Disabled

NO TOOLS

inventory-api

Private

6 TOOLS

SaaS catalog

Browse a growing catalog of pre-built MCP servers for tools like GitHub, Linear, and Sentry. Deploy in one click.

Internal APIs

Turn any internal API into an MCP server by pointing at your API definition. Cursor reaches your proprietary systems in minutes.

Secure by default

Credentials stay vaulted and are never exposed to the model. Every tool call runs through policy checks and lands in an audit log.

Token-efficient

Curate tools into focused toolsets and utilize code mode to reduce token usage and improve agent accuracy.

Provision

Provision access across the org

Enterprise-grade permissions, credential management, and per-team provisioning. Control who reaches which tools, down to the individual.

OAuth 2.1 built in

Every server gets OAuth 2.1 with DCR and PKCE out of the box. Plug in existing SSO and skip the auth plumbing.

Per-team registries

Provision a scoped catalog to each team. Roll out to one team at a time without opening access to the whole org.

Team access control

OAuth 2.1

Engineering24 members

Full access

GitHubread-write

Linearread-write

Slackread-write

Notionread-only

internal-billing-apiread-write

Product12 members

Standard

Linearread-write

Figmaread-only

Slackread-write

Notionread-write

Customer Success8 members

Standard

Slackread-write

Gmailread-write

Notionread-only

Finance5 members

Restricted

internal-billing-apiread-only

Gmailread-write

Scoped access

Role-based permissions at the server, toolset, and individual tool level. Every team sees exactly what they need.

Full audit trail

Every tool call, permission change, and access event logged and searchable. SOC 2 Type II and ISO 27001 certified.

Team access control

OAuth 2.1

Engineering24 members

Full access

GitHubread-write

Linearread-write

Slackread-write

Notionread-only

internal-billing-apiread-write

Product12 members

Standard

Linearread-write

Figmaread-only

Slackread-write

Notionread-write

Customer Success8 members

Standard

Slackread-write

Gmailread-write

Notionread-only

Finance5 members

Restricted

internal-billing-apiread-only

Gmailread-write

OAuth 2.1 built in

Every server gets OAuth 2.1 with DCR and PKCE out of the box. Plug in existing SSO and skip the auth plumbing.

Per-team registries

Provision a scoped catalog to each team. Roll out to one team at a time without opening access to the whole org.

Scoped access

Role-based permissions at the server, toolset, and individual tool level. Every team sees exactly what they need.

Full audit trail

Every tool call, permission change, and access event logged and searchable. SOC 2 Type II and ISO 27001 certified.

Monthly budgetsEnforced in real time

PlatformWithin budget

$6,800 / $10,000

SupportApproaching limit

$4,150 / $5,000

DataCapped

$9,100 / $9,000

GrowthWithin budget

$1,900 / $6,000

Cost

Control Cursor spend

Attribute every token to a team, set budgets, and cap runaway usage before it lands on the bill. No more guessing where spend goes.

Per-team budgets

Real-time caps

Spend by team

Break down Cursor usage and cost by team, role, and individual. Know exactly who is driving spend.

Budgets and caps

Set monthly budgets per team and enforce them in real time. Usage stops at the limit instead of overrunning it.

Token attribution

Every tool call carries its token cost back to a team and a user, so chargebacks and forecasts hold up.

No surprise bills

Alerts fire as teams approach their limit. Leadership sees spend trending before the invoice arrives.

Cost

Control Cursor spend

Attribute every token to a team, set budgets, and cap runaway usage before it lands on the bill. No more guessing where spend goes.

Per-team budgets

Real-time caps

Monthly budgetsEnforced in real time

PlatformWithin budget

$6,800 / $10,000

SupportApproaching limit

$4,150 / $5,000

DataCapped

$9,100 / $9,000

GrowthWithin budget

$1,900 / $6,000

Spend by team

Break down Cursor usage and cost by team, role, and individual. Know exactly who is driving spend.

Budgets and caps

Set monthly budgets per team and enforce them in real time. Usage stops at the limit instead of overrunning it.

Token attribution

Every tool call carries its token cost back to a team and a user, so chargebacks and forecasts hold up.

No surprise bills

Alerts fire as teams approach their limit. Leadership sees spend trending before the invoice arrives.

Secure

Secure every interaction

Every prompt, response, and tool call is inspected in real time. Block data from leaving and catch threats before they reach your systems.

Block data loss

Source code, PII, secrets, and credentials are redacted or blocked before they leave the org. Exfiltration patterns are stopped in flight.

Prompt injection defense

Inspect tool calls and responses for injection attempts, so a poisoned tool or repo cannot redirect Cursor against your data.

Data loss prevention

Active

TimePattern / SampleSessionTypeAction

Shadow tool detection

Surface unsanctioned MCP servers and tools the moment they appear, instead of finding them in an incident review.

SIEM and audit

Alerts route to your existing SIEM and a full audit trail records who asked what, when, against which data.

Data loss prevention

Active

TimePattern / SampleSessionTypeAction

Block data loss

Source code, PII, secrets, and credentials are redacted or blocked before they leave the org. Exfiltration patterns are stopped in flight.

Prompt injection defense

Inspect tool calls and responses for injection attempts, so a poisoned tool or repo cannot redirect Cursor against your data.

Shadow tool detection

Surface unsanctioned MCP servers and tools the moment they appear, instead of finding them in an incident review.

SIEM and audit

Alerts route to your existing SIEM and a full audit trail records who asked what, when, against which data.

Every agent

One control plane for every agent

Teams rarely settle on a single agent. The same rollout, oversight, and cost controls apply across Claude, ChatGPT, Cursor, and the agents your teams build themselves.