How to connect Stripe to ChatGPT: the plugin, MCP, and your metrics

ChatGPT is where a lot of founders already live, and Stripe is where their money already lives. Wiring the two together is now genuinely easy, but the wiring comes in two distinct forms that most guides blur together, and picking the wrong one for your question is how you end up with an agent confidently miscalculating your MRR.

Form one is Stripe's official integration: ChatGPT gets the Stripe API as tools, so it can look up customers, chase invoices and issue refunds. Form two is a metrics connector: ChatGPT gets computed subscription analytics (MRR, churn, cohorts, LTV), so it can answer "how is the business doing" questions with numbers that are actually right. This guide sets up both and is honest about which questions belong to which.

Form one: the official Stripe integration

Stripe ships a first-party path for OpenAI's products. In ChatGPT itself, it is a plugin you install from the store; in the Codex CLI, it is a standard MCP entry pointing at https://mcp.stripe.com:

claude mcp add --transport http stripe https://mcp.stripe.com/

{
  "mcpServers": {
    "stripe": {
      "url": "https://mcp.stripe.com"
    }
  }
}

[mcp_servers.stripe]
url = "https://mcp.stripe.com"

# then, in the terminal:
codex mcp login stripe

Authentication is OAuth: Stripe opens a consent screen, you choose the account, and the session appears under OAuth sessions in your Stripe user settings, where you can revoke it any time. No API key touches ChatGPT.

What you get is operational reach. The Stripe tools can search the API, read your account data, and, importantly, write: refunds, subscription changes, invoice operations. Ask it to find a payment and refund it, and it will. Two consequences follow:

1. Keep confirmation on for tool calls that modify anything, and read what ChatGPT proposes before approving. Stripe's own docs say the same.
2. If you only want lookups, connect with a restricted API key limited to read permissions instead of OAuth.

The full tool list and where its limits are is a post of its own: the Stripe MCP server, explained.

Form two: your metrics, over MCP

Now the trap. With the Stripe integration connected, ask ChatGPT "what is my churn rate this quarter" and it will gamely page through raw subscription objects and improvise an answer. The improvisation is the problem: churn, MRR and LTV are computations with edge cases (annual normalization, proration, dunning, coupons), and a model re-deriving them from raw API objects gets a slightly different wrong answer each time. The number sounds right, cites real customers, and does not survive an audit.

The fix is to compute first and let ChatGPT read the results. Kometrics syncs your Stripe history, classifies every dollar into a movement ledger (new business, expansion, contraction, churn, reactivation), and serves the finished metrics over MCP. ChatGPT connects to it through Developer mode:

claude mcp add --transport http kometrics https://app.kometrics.com/mcp

codex mcp add kometrics --url https://app.kometrics.com/mcp
codex mcp login kometrics

Getting Stripe into Kometrics first is the usual five minutes: create a workspace, open Settings then Sources, pick Stripe, and connect with OAuth or a restricted read key plus the webhook shown. The sync rebuilds your history back to the first invoice.

The connector is OAuth too, with one deliberate difference from form one: every tool is read only. There is no refund tool, no cancel tool, no write path at all, so this connection never enters the "what could the agent break" conversation.

What it looks like in practice

The payoff question for ChatGPT specifically is drafting: it is where investor updates, board notes and summaries get written, and a metrics connector means the numbers arrive in the draft already correct:

Prompts that earn the connection:

• Why was MRR flat last month?
• Which customers churned in the last 90 days, and what did they carry?
• How does the January signup cohort retain against December’s?
• What is our LTV, and how has it moved over the last six months?
• Which accounts renew in the next 30 days?

One decision table

FAQ

Can ChatGPT connect to Stripe directly?

Yes. Stripe publishes an official plugin for ChatGPT (Plus, Pro, Business, Enterprise and Education plans) and an MCP server at https://mcp.stripe.com that the Codex CLI and other MCP clients use. Both authenticate with OAuth.

Do I need a paid ChatGPT plan?

For the Stripe plugin and for custom MCP connectors, yes: both live in features free accounts do not have. The Codex CLI follows its own plan requirements.

Is it safe to give ChatGPT access to Stripe?

The OAuth sessions are revocable from your Stripe dashboard, and administrators can manage MCP access account-wide. The risk to actually manage is write access: keep tool confirmation on, or use a read-only restricted key. A metrics connector like Kometrics is read only by construction, which removes the question entirely for that half.

Can ChatGPT calculate MRR from raw Stripe data?

It will produce a number; it will not reliably produce the right one. MRR needs consistent policies for annual plans, trials, proration, coupons and failed payments applied across the whole history, which is ledger work, not chat work. What is MRR shows exactly where the improvised versions break.

Does this work the same in Claude?

Yes, both forms: same endpoints, same OAuth, different client menus. The Claude walkthrough is here.