How to Connect ChatGPT to Stripe with MCP

Connecting ChatGPT to Stripe lets you ask about customers, payments, invoices and subscriptions in plain English, and have ChatGPT make supported changes such as creating an invoice. It can also search Stripe's documentation for you. Stripe hosts the server at mcp.stripe.com and links to an official Stripe plugin in ChatGPT.

Checked against: Stripe's MCP documentation and OpenAI's guide to connected apps in ChatGPT on 28 October 2026. eSEOspace did not run these steps; menus can change, so follow the vendor's page if it differs.

Before you start

You need a ChatGPT account and a Stripe account. OpenAI's plugins article says the plugin directory is available across ChatGPT plans, but installing or using an individual plugin depends on your plan, workspace, role and region. Stripe does not list a separate price for MCP access.

In a ChatGPT Business workspace, OpenAI says apps are enabled by default and admins can change that. In Enterprise and Edu, new plugins and apps are disabled by default, so an admin may need to enable Stripe first.

On the Stripe side, an administrator can turn MCP access on or off on the MCP and CLI access settings page. Live mode and sandboxes are set separately. If your company manages your device or network, Stripe says to ask IT to allow mcp.stripe.com.

Steps

Option 1: Install the Stripe plugin (Stripe's documented route)

Stripe's ChatGPT instructions are short: install the official Stripe plugin in ChatGPT, then connect your Stripe account and grant permissions in the OAuth window. OpenAI's connected apps article gives the ChatGPT side:

1. Open Settings > Plugins and select Stripe, or open Stripe's install link above.
2. Select Install plugin if shown.
3. If prompted, select Connect.
4. Sign in to your Stripe account. Stripe's consent page lets you pick one or more live mode accounts or sandboxes and set permissions for each.
5. Review the requested permissions and finish the authorization.
6. In a conversation, type @ and pick Stripe, or select + and choose it.

If you want to test safely, grant a sandbox only. You can reconnect later to add live mode.

Option 2: Add Stripe as a custom MCP server

For other clients, Stripe says to use this server URL and OAuth when the client supports it:

https://mcp.stripe.com

OpenAI's custom MCP server article says custom connections are for ChatGPT Business and Enterprise/Edu on the web. On Business, only admins and owners can create them. Pro users can connect custom servers with read and fetch permissions only. The steps are:

1. Go to Plugins.
2. Select the plus button, then Add custom MCP server.
3. Enter a name and, optionally, a description.
4. Under Connection, enter https://mcp.stripe.com.
5. Configure authentication for the server.
6. Review the risk warning and select I understand and want to continue.
7. Select Create as a plugin, then review the discovered tools.

Most teams should use Option 1, since it is the route Stripe documents for ChatGPT.

Check that it works

Start with read-only questions, and approve each action while you check the results.

Example prompts:

• "@Stripe get my account info and tell me which account you're connected to." (uses get_stripe_account_info)
• "List my 10 most recent charges with the amount, currency and status of each." (uses stripe_api_read)
• "Search the Stripe documentation for how to set up a customer portal." (uses search_stripe_documentation)

Permissions and safety

Stripe's server reads and writes. stripe_api_read runs supported GET methods, and stripe_api_write runs supported POST, PATCH, PUT and DELETE methods. The supported list includes creating refunds, voiding invoices and cancelling subscriptions.

• Human confirmation. Stripe requires confirmation before certain stripe_api_write actions, such as refunds and outbound payments. You click the agent's link, review the request and click Approve, then tell the agent to retry. Approvals expire after 24 hours.
• ChatGPT approvals. Stripe asks you to turn on your client's tool-approval setting. OpenAI's app permissions article lists Always ask, Allow read actions, Allow low-risk actions and Allow all actions. For Stripe, Always ask or Allow read actions is the cautious choice.
• Revoke access. Your authorized clients appear under OAuth sessions in your Stripe user settings. Use the overflow menu and select Revoke access.
• Prompt injection. Stripe warns to take care when you use its server alongside other servers. Read MCP prompt injection and the MCP Security Center.

If it doesn't work

• Blocked network. Stripe says managed devices or networks may block external MCP servers. Ask IT to allow mcp.stripe.com.
• "Disabled by admin" or "Admin approval required." OpenAI's troubleshooting article says to ask your workspace administrator to review the plugin and its app.
• MCP turned off in Stripe. A Stripe admin may have disabled MCP access for live mode or sandboxes.
• API key errors. From December 2026, Stripe MCP stops accepting full-access secret keys and restricted keys without the Agent tag. Requests with those keys get a 401. Reconnect with OAuth or use an agent API key.

Next step

Read the Stripe MCP server profile for the full tool list and the 30 November 2026 key deadline. For a store-wide view, see MCP for ecommerce. More setup guides live in the connection guides hub, including Claude with Stripe.

Frequently asked questions