Skip to main content
Back to the Stripe MCP server

MCP Gateway · Claude Cowork

Stripe icon

Connect Stripe to Claude Cowork

Some Stripe jobs touch dozens of records, like answering every open dispute or closing out month-end billing, and Cowork can carry them through in one session. The Stripe plugin arrives from the marketplace your admins sync into Claude, prompts are checked by Speakeasy as each step starts, and the session is attributed to whoever ran it.

Category
Sales & CRM
Tools
31
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Stripe server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Stripe from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Stripe

Work through open disputes

Cowork lists open disputes, gathers the related charge and customer details for each, and submits evidence on every dispute you approve.

list_disputesfetch_stripe_resourcesupdate_dispute

Prepare month-end invoices

Cowork goes through a list of customers, adds the month's invoice items, finalizes each invoice, and reports any customer where a step failed.

create_invoice_itemcreate_invoicefinalize_invoice

Summarize refunds for finance

Cowork lists the month's refunds, checks the current balance and writes a summary the finance team can file with its month-end notes.

list_refundsretrieve_balance

Tools

31 tools

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

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

How do members get the Stripe plugin in Cowork?
An admin syncs the organization's plugin repository under Organization settings > Plugins & skills and sets the plugin that carries Stripe to Available to install or Installed by default. Members who receive plugins through Cowork don't need a GitHub invitation.
Can a Cowork prompt about Stripe be blocked?
Yes. Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs. On Claude Enterprise, prompts can also be checked before inference (beta).
How do Claude Cowork users get Stripe?
An admin adds Stripe from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Stripe tools their access allows.
Are Stripe calls from Claude Cowork 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.