Skip to main content
Back to the Stripe MCP server

MCP Gateway · Codex

Stripe icon

Connect Stripe to Codex

Codex can help plan a Stripe integration, then test its code against your real account. Through the Speakeasy MCP Gateway, an admin picks which of the 31 Stripe tools engineers may use, and each Codex call is inspected for prompt injection and logged under the engineer who started it.

Category
Sales & CRM
Tools
31
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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 Codex 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 Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Stripe from Codex

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

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Stripe

Plan which Stripe products to use

Describe the payment flow you need, and Codex works through Stripe's integration recommender to choose between products such as Checkout, Elements or Billing before writing code.

stripe_integration_recommender

Check the docs for your language

Codex searches Stripe's documentation for the language your project uses, so the code it writes follows the documented approach rather than memory.

search_stripe_documentation

Call an operation without a dedicated tool

For an endpoint the named tools don't cover, Codex looks up the operation ID, reads its parameters, then executes it against Stripe.

stripe_api_searchstripe_api_detailsstripe_api_execute

Tools

31 tools

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

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

Prompt and tool-call blocking

Codex

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Are Codex cloud tasks covered when they call Stripe?
No. Codex cloud tasks and GitHub code review run off the device, and neither the plugin nor OpenTelemetry covers them. OpenAI's Compliance Logs record them after the fact.
Do engineers need a Stripe API key in Codex?
No. Agents reach Stripe through the gateway and never hold a Stripe credential. Each session signs in through your identity provider.
How do Codex users get Stripe?
An admin adds Stripe from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Stripe tools their access allows.
Are Stripe calls from Codex 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.