MCP Gateway · Cursor
Connect Stripe to Cursor
Cursor can check how your Stripe account is set up while you write billing code in the editor. The Speakeasy MCP Gateway gives each developer the same Stripe URL, applies their role's rules to every tool call, and ties each call to the developer's email.
- Category
- Sales & CRM
- Tools
- 31
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Stripe MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Stripe call inspected and logged.
Set up
Add Stripe to Cursor in 4 steps
- 01
Add Stripe from the catalog
An admin finds Stripe 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.
Stripe 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 Stripe
Give teams the
mcp:connectscope on the Stripe server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Stripe 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 Stripe from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Stripe needs its own OAuth grant, so each person connects it once. Until they do, Stripe calls fail while the rest of the gateway keeps working.
From then on, Stripe'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 Stripe
Match code to real prices
List the products and prices in Stripe so Cursor puts the right price IDs in your pricing page or plan config instead of placeholders.
Test an upgrade flow
While building plan upgrades, Cursor lists a test customer's subscriptions and updates one, so you can see how your code handles the change.
Search records by field value
Use Stripe's query syntax to find customers, charges or payment intents by a field such as email or metadata, then step through your code with those records.
Tools
31 tools
Each Stripe tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
search_stripe_documentation
Search the Stripe documentation for the given question and language.
get_stripe_account_info
This will get the account info for the logged in Stripe account.
create_customer
This tool will create a customer in Stripe.
list_customers
This tool will fetch a list of Customers from Stripe.
create_product
This tool will create a product in Stripe.
list_products
This tool will fetch a list of Products from Stripe.
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 Stripe call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Stripe tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Stripe 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
Does Cursor fail open if Speakeasy can't be reached?
How does a Cursor team get Stripe without GitHub access?
How do Cursor users get Stripe?
Are Stripe calls from Cursor logged?
Connect more