Skip to main content
Back to the Stripe MCP server

MCP Gateway · Claude

Stripe icon

Connect Stripe to Claude

Finance and support staff can ask Claude about customers, invoices and refunds in Stripe without opening the dashboard. Through the Speakeasy MCP Gateway, each person connects from Customize > Connectors, sees only the Stripe tools their role can reach, and every call they make is logged.

Category
Sales & CRM
Tools
31
Authentication
OAuth
Claude
Web, desktop and mobile

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.

Deploy on MCP Gateway

Set up

Add Stripe to Claude in 4 steps

  1. 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.

  2. 02

    Choose who can use Stripe

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Stripe from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Stripe

Answer a customer's billing question

Ask Claude for a customer's recent invoices and refunds, and get a plain summary of what they were charged and what was paid back.

list_customerslist_invoiceslist_refunds

Create and finalize an invoice

Claude adds the line items to a new invoice for a customer and finalizes it, so it is ready to send without opening Stripe.

create_invoicecreate_invoice_itemfinalize_invoice

Check the balance before a meeting

Ask for the current Stripe balance before a finance meeting and get it next to the details of the connected account.

retrieve_balanceget_stripe_account_info

Tools

31 tools

Each Stripe tool can be allowed or denied per team and role at the MCP Gateway before Claude 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.

See all 31 tools

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Speakeasy block a Stripe request in Claude before it runs?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Can a finance team use Stripe in Claude without issuing refunds?
Yes. Admins decide which of the 31 Stripe tools each team can call, so finance could list refunds without access to create_refund.
How do Claude users get Stripe?
An admin adds Stripe from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Stripe tools their access allows.
Are Stripe calls from Claude logged?
Yes. Stripe calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Stripe in other clients

AI everywhere.

Control here.