Stripe + ChatGPT
Connect Stripe to ChatGPT
with OpenAI models and the Agent200 SDK
ChatGPT cannot send an API key to a custom MCP server, so this guide builds Stripe into your own agent with OpenAI's models and the Agent200 SDK.
On this page
Overview
ChatGPT can add custom MCP servers, but it signs in to them only with OAuth or with no sign-in, and cannot send an API key. Agent200’s MCP server uses your API key, so this guide takes the SDK route: you build Stripe into your own agent with OpenAI’s models, through Agent200.
Your agent then calls the Stripe tools with each user’s own Stripe connection: Agent200 runs the OAuth flow, stores the tokens and keeps them fresh.
- Connector
- Stripe
- Works with
- ChatGPT · Your own agent code
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 9 tools
- Model in examples
openai/gpt-5.6-sol
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Stripe enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Stripe account. They approve access once, on Stripe's own page.
- A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.
Connect Stripe to ChatGPT
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Stripe and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Set up the Agent200 SDK
Add the SDK to your project and create a client with the key from the environment.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
3
Step 3: Let your user connect Stripe
Each end user authorizes their own Stripe account once, through managed OAuth. If the user has not connected yet, Agent200 returns an authorization link: show it to them, and they approve access on Stripe's own page. Agent200 handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Stripe account, once. const connection = await agent200 .user("user_123") .connect("stripe"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
4
Step 4: Run with the Stripe tools
Name the user, the model and Stripe in the tools. The model decides when a Stripe tool is needed, and Agent200 executes the call with the user's own connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "How much did we take in payments this week", tools: ["stripe"], }); console.log(result.output);
Test your connection
Run one request to check everything is wired up.
Ask
How much did we take in payments this week
What should come back
-
An answer in
result.output, built from the user's own Stripe data. -
Behind the scenes, the model calls a Stripe tool, such as
stripe_search_customers, and Agent200 runs it.
If Agent200 returns an authorization link instead, the user has not connected Stripe yet. Go back to the connect step.
Get your API key
Create a key in the Agent200 dashboard. It reaches Stripe and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Stripe to ChatGPT.
Goal: connect Stripe to ChatGPT with Agent200. Guide: https://www.agent200.com/tools/stripe/framework/chatgpt/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Make sure Stripe is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs. 3. Add the Agent200 SDK to the project and create a client with that key. 4. Give every request a stable id for the end user. Agent200 uses only that user's own connections. 5. Connect the user's Stripe account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on Stripe. 6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "stripe" in the tools. The model decides when a Stripe tool is needed; Agent200 executes the call. 7. Check it works with this request: "How much did we take in payments this week" What should come back: - An answer in `result.output`, built from the user's own Stripe data. - Behind the scenes, the model calls a Stripe tool, such as `stripe_search_customers`, and Agent200 runs it. 8. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Stripe, then retry. The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
The whole guide is also available as Markdown, for agents and LLMs: /tools/stripe/framework/chatgpt.md
Stripe tools ChatGPT can call
-
Search customers
Readstripe_search_customersFind customers by email, name or metadata.
-
Create a customer
Writestripe_create_customerAdd a customer with a name and email address.
-
List payments
Readstripe_list_paymentsList recent payments with their amount and status.
-
Get the balance
Readstripe_get_balanceRead the account's available and pending balance.
-
List invoices
Readstripe_list_invoicesList invoices by customer or status, such as open or paid.
-
Create an invoice
Writestripe_create_invoiceCreate a draft invoice for a customer.
-
Send an invoice
Writestripe_send_invoiceEmail a finalized invoice to the customer.
-
Create a payment link
Writestripe_create_payment_linkCreate a link where a customer can pay for a product.
-
List subscriptions
Readstripe_list_subscriptionsList subscriptions by customer or status.
No tool matches that search.
How it works
-
01
Your app sends the request
It calls Agent200 with the model, instructions, the input, the end user's id and the Stripe tools.
-
02
The model picks a tool
The model decides whether a Stripe tool is needed, and with which arguments.
-
03
Agent200 runs the call
It uses that user's own Stripe connection, within the endpoints and scopes your project allows, and returns the result to the model.
-
04
Your app gets the result
Agent200 returns the completed result. Your app decides when the agent runs and what happens next.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Stripe account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Stripe enforces what its API grants.
Troubleshooting
Why not add Agent200 to ChatGPT as an MCP server?
ChatGPT’s custom MCP servers sign in with OAuth or with no sign-in, and cannot send an API key. Agent200’s MCP server uses your API key, so for ChatGPT users the SDK route on this page is the one that works.
The request says Stripe authorization is required
The end user has not connected Stripe yet, or the connection needs to be approved again. Agent200 returns an authorization link: show it to the user, let them approve access on Stripe's own page, then run the request again.
ChatGPT does not use the Stripe tools
Check that Stripe is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Stripe in the request, or in the instructions, also helps the model choose the right tool.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows (services, endpoints and scopes), and Stripe returns only what the end user authorized. Widen the endpoints or scopes in the dashboard if the agent needs more, then ask the user to connect Stripe again so they can approve the new access.
The results come from the wrong account
Every request names an end user (user_123 in the examples). Pass the id of the person your agent is working for: Agent200 then uses only that user's Stripe connection, never another user's.
The API key was pasted into a chat or committed
Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.