MCP Gateway · Claude Code
Connect Stripe to Claude Code
Claude Code can look up Stripe objects and API details while you build or debug a payments integration in the terminal. Through the Speakeasy MCP Gateway, each developer reaches Stripe at one URL, calls only the tools their role allows, and every Stripe call is logged against their name.
- Category
- Sales & CRM
- Tools
- 31
- Authentication
- OAuth
- Claude Code
- CLI
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 Claude Code 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 Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Stripe from Claude Code
The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Stripe
Inspect the object behind a webhook
When a webhook handler fails, give Claude Code the ID from the event and it fetches the full Stripe object, so you can compare the real payload with what your code expects.
Find the right API operation
Search Stripe's API operations by keyword and pull the full parameter list for the one you need, before Claude Code writes the call in your code.
Seed test data for a feature
Create a customer, a product and a price from the terminal so the checkout flow you're building has something real to charge against.
Tools
31 tools
Each Stripe tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can I stop Claude Code from creating refunds in Stripe?
Can Stripe in Claude Code be rolled out to the whole team?
How do Claude Code users get Stripe?
Are Stripe calls from Claude Code logged?
Connect more