MCP Gateway · Cursor
Connect Ramp to Cursor
Engineering leads who live in Cursor still own a budget. The agent can read Ramp spend data in the editor, next to the infrastructure and vendor code that drives it. Cursor hooks send each prompt and tool call to Speakeasy for a decision before it runs, and every hook event carries the user's email.
- Category
- Sales & CRM
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Ramp MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Ramp call inspected and logged.
Set up
Add Ramp to Cursor in 4 steps
- 01
Add Ramp from the catalog
An admin finds Ramp in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Ramp uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Ramp
Give teams the
mcp:connectscope on the Ramp server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Ramp to their gateway on the next call, and removing it takes it away. - 03
Connect Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Ramp from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Ramp needs its own OAuth grant, so each person connects it once. Until they do, Ramp calls fail while the rest of the gateway keeps working.
From then on, Ramp's tools appear in Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Ramp
Price a migration plan
While drafting a design document in Cursor, pull current Ramp spend for the services you plan to replace, so the cost section uses real numbers.
Find unused developer tool subscriptions
Read Ramp spend on developer tools and compare it with the SDKs and services your code still imports, so you can cancel what nobody uses.
Check a vendor before renewing
When a contract renewal lands on your desk, ask Cursor what the team spent with that vendor over the past year and how the spend changed month by month.
Control
What Speakeasy can see and stop in Cursor
The gateway covers every client the same way. The rest depends on what Cursor exposes to Speakeasy.
Tool logs
Gateway
Every Ramp call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Ramp tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Ramp can reject a tool request before it reaches the server, or withhold a result from Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Can Speakeasy stop Cursor from reading Ramp data?
Can I see Cursor's own spend next to Ramp?
How do Cursor users get Ramp?
Are Ramp calls from Cursor logged?
Connect more