Skip to main content
Back to the Stripe MCP server

MCP Gateway · OpenCode

Stripe icon

Connect Stripe to OpenCode

OpenCode can query and change Stripe from the terminal while you work on payment code. Put the Stripe server's hosted URL in the mcp block of your OpenCode config, restart and sign in, and each Stripe call then goes through the Speakeasy gateway under your role.

Category
Sales & CRM
Tools
31
Authentication
OAuth
OpenCode
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.

Deploy on MCP Gateway

Set up

Add Stripe to OpenCode 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. OpenCode 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 OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Stripe from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Stripe

Trace a payment that failed

OpenCode finds the customer and lists their recent payment intents, so you can see which one failed and match it with the request in your logs.

list_customerslist_payment_intents

Refund a test payment

After testing a checkout change, OpenCode refunds the payment intent you created and lists recent refunds to confirm it went through.

create_refundlist_refunds

Create a payment link for QA

Generate a payment link for a test price so QA can run through the purchase flow without needing a build of the app.

create_payment_link

Tools

31 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

Can Speakeasy block a Stripe refund from OpenCode?
Yes. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs. Admins can also deny create_refund for a role at the gateway.
Where does OpenCode's token usage come from?
Token and cost totals flow through the OpenCode plugin, reported per turn. OpenCode has no OpenTelemetry exporter.
How do OpenCode users get Stripe?
An admin adds Stripe from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Stripe tools their access allows.
Are Stripe calls from OpenCode 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.