How to connect Stripe to Claude (and actually ask about your revenue)

Once Claude can see your Stripe account, a category of busywork disappears. Refunds happen in a sentence. "Who paid us today" stops requiring a dashboard login. Your monthly investor update pulls its own numbers. This guide is the whole setup, end to end, in about ten minutes.

One thing most guides skip: there are two different connections hiding behind "connect Stripe to Claude", and which one you want depends on the question you plan to ask.

Most SaaS founders end up wanting both, and they do not conflict. Set them up in either order.

Route A: the official Stripe MCP server

Stripe hosts a remote MCP server at https://mcp.stripe.com. Nothing to install or deploy; you add the URL to your client and approve an OAuth screen:

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

Once connected, Claude can search the Stripe API, read your account data, and act on it. Prompts that earn their keep immediately:

• Refund the last charge from acme.io.
• Create a $49/month price on the Pro product and give me a payment link.
• List the invoices that are past due and draft a reminder email for each.
• Which disputes are open right now, and when is the evidence due?

Two cautions before you hand it live-mode access. First, this server writes: it can refund charges, cancel subscriptions and void invoices, so keep Claude's tool confirmation on and review what it proposes before approving. Second, if a workflow only ever reads, connect it with a restricted API key that has no write permissions instead of OAuth. We went deep on the tool list and the security model in the Stripe MCP server, explained.

Route B: your metrics, computed before Claude asks

Here is the wall you will hit with Route A: ask "what was my MRR growth last month, split by new business, expansion, contraction and churn" and Claude has to page through raw subscription objects and do the math itself. MRR is not a field in the Stripe API; it is a computation full of judgment calls (annual plans, proration, trials, coupons, past-due accounts), and a model improvising that computation in-context produces a different wrong number every time you ask.

The fix is to put a metrics layer between Stripe and Claude. Kometrics syncs your billing data and normalizes it into a movement ledger: every dollar of new business, expansion, contraction, churn and reactivation, per customer, per month. Claude then reads finished metrics over MCP instead of computing its own.

The setup has two halves. First, Stripe into Kometrics:

1. Create a workspace (free under $1,000 MRR, no card).
2. Open Settings, then Sources, and pick Stripe from the tile.
3. Connect with one-click OAuth, or paste a restricted read key and add the webhook shown.
4. The sync runs, and your MRR, movements and customer history appear in a couple of minutes.

Then Kometrics into Claude:

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

There is no API key in this half at all: Claude registers itself over OAuth, you approve it on a Kometrics screen, and you pick which workspace it may read there. Every tool it gets is read only, so this connector never needs to appear in your "what can my agents break" threat model.

What asking actually looks like

That per-customer, per-movement specificity is the point of Route B. The number Claude cites is the same one the dashboard renders, computed once from the ledger, so you can click through and verify rather than trust:

app.kometrics.com/ai

Prompts to start with once you are connected:

• 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?

Which route do you need?

• You mostly operate: refunds, payment links, invoice chasing, support lookups. Route A alone covers you.
• You mostly ask: growth, churn, cohorts, board numbers. Route B alone covers you, and it also reads Paddle, Creem and Asaas if Stripe is not your only biller.
• You are a founder: realistically both, one conversation. "Why did MRR dip, and pause the subscription of whoever disputed that charge" uses each connector for its half.

FAQ

Can Claude connect to Stripe directly?

Yes. Stripe hosts an official MCP server at https://mcp.stripe.com that Claude, Claude Code, Cursor and Codex connect to over OAuth. No third-party bridge is needed for raw account access.

Is it safe to give Claude access to Stripe?

OAuth-based connections are revocable in your Stripe user settings, and MCP access can be managed account-wide by administrators. The real risk to 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, so it carries no write risk at all.

Does this work on the free Claude plan?

Custom connectors (both routes here) require a paid Claude plan. Claude Code and the Codex CLI follow their own product's plans.

Can Claude calculate my MRR from Stripe?

It will try, and it will be subtly wrong: annual normalization, proration, trials, coupons and past-due handling each need a consistent policy applied across your whole history. That is what a subscription analytics layer is for; What is MRR? walks through exactly where naive computations break.