Configure the Stripe MCP Server

Overview

Stripe operates an official hosted MCP server at mcp.stripe.com, exposing named tools such as list_available_accounts_or_orgs and get_stripe_account_info alongside dynamic passthrough tools (stripe_api_read, stripe_api_write, stripe_api_search, stripe_api_details) that can call almost any Stripe API method.

1. Add the MCP server to your gateway config

Go to your gateway in the Dtwo UI and open Configuration → Advanced. In the mcp_servers section add the following entry:

  - name: stripe
    description: "Stripe's official hosted MCP server."
    url: https://mcp.stripe.com
    transport_type: streamablehttp
    authentication:
      type: oauth
      grant_type: authorization_code
      issuer: "https://access.stripe.com/mcp"
      redirect_uri: "<CALLBACK_URL>"
      scopes:
        - mcp
      pkce_enabled: true

Replace the placeholder value:

• <CALLBACK_URL> — your Dtwo gateway’s OAuth callback URL, found in the Overview tab for your gateway in the Dtwo UI.

2. Deploy and verify

Save the configuration and deploy the gateway.

Then, in your AI client, ask it to authorize Stripe via the gateway. This opens Stripe’s OAuth consent page — sign in as the Stripe user whose account access the agent should inherit, and approve the consent prompt. Once authorized, confirm the server’s tools appear, then call a read-only tool such as get_stripe_account_info to confirm the connection works before exercising a write tool (such as a refund).

If the tools don’t appear after you authorize, refresh the tool list in your AI client — some clients don’t pick it up automatically.