stripe-founder-mcp is the Stripe co-pilot for indie SaaS founders. It connects your Stripe account to any MCP-compatible AI client — Claude Desktop, Claude Code, Cursor, ChatGPT, Windsurf — and lets you ask questions about your business in plain English.

The problem this solves: Stripe's API is exhaustive but the Dashboard requires clicking through ten screens to answer simple questions, and the existing Stripe MCPs on the market are thin CRUD wrappers that just let an AI list charges or retrieve a customer object. They don't answer founder questions.

This MCP is opinionated. Every tool maps to a question a founder actually asks — "What's my MRR?", "Who's about to churn?", "Is dunning recovering my failed payments?" — with the math done correctly and the output shaped for an LLM to summarize naturally. Headline number first, supporting context after, raw line items last.

What you can ask:

"What's my MRR right now and how does it compare to last month?"
"Who's at risk of churning this week, and how much MRR is at stake?"
"Summarize all failed payments from the past 7 days. Which ones still might recover?"
"How well is dunning working this month?"
"Give me a churn breakdown for Q1 — voluntary vs involuntary, top reasons."
"Tell me everything about acme-corp.com — payment history, plan, lifetime value."
"I'm handling a support ticket about a refund. Pull up everything I need."
"Who signed up in the last 30 days, how many converted to paid, and what's the new MRR?"
"Are there any open disputes I need to respond to, and when are the deadlines?"
"What's my net new MRR and growth rate this month?"

The 9 tools:

get_mrr — current MRR with month-over-month delta, plus trialing subscriptions tracked separately as potential MRR (correctly excluded from headline MRR per Baremetrics/ChartMogul standards)
get_growth_metrics — new MRR, expansion, contraction, churned MRR, net new MRR, and growth rate for any period
get_churn_summary — voluntary vs involuntary breakdown, gross and net churn rates, top cancellation reasons aggregated from cancellation_details
get_failed_payment_recovery_rate — how well your dunning is recovering failed payments, with the top 5 unrecovered failures by amount surfaced for follow-up
list_at_risk_customers — past-due, recent failures, and multi-attempt retry signals combined into a ranked list sorted by MRR at risk
list_recent_signups — new customers in any window with paid-conversion count and total new MRR
list_disputes — open chargebacks with evidence deadlines, plus filtered views for won/lost history
get_customer_profile — full snapshot for one customer including LTV, plan, payment method status, tenure, and a chronological timeline of recent activity
get_support_context — everything needed to handle a support ticket: risk flags (in_dunning, recent_dispute, trial_ending_soon, high_value, new_customer), refund-eligible charges, and a timeline reordered by ticket context (mention "refund" and refund events surface first)

Built for trust:

Read-only enforced at runtime. A guard blocks any non-GET Stripe request at the HTTP client level. There are zero write paths in the codebase.
Restricted-key recommended. Use a Stripe restricted key (rk_live_...) scoped to read access only — never your full secret key.
Test mode auto-detected. Every response includes stripe_mode: "test" or "live" so you never confuse environments mid-conversation.
Multi-currency aware. Mixed-currency accounts return per-currency breakdowns with explicit caveats rather than silently summing across currencies.
No telemetry. No data leaves your machine beyond the calls to Stripe's API.
Open source under MIT. Audit the code before you trust it with your Stripe key.

Built for AI agents:

All tools accept human-readable date ranges: "last_30_days", "this_month", "2026-Q1", "March 2026", or explicit ISO ranges
get_customer_profile and get_support_context accept email, name, or Stripe customer ID — the LLM doesn't need to resolve IDs first
Every money field returns both amount_cents and a formatted string so LLMs can compute and humans can read
Tool descriptions are written for LLM tool-selection accuracy, not for human docs
60-second response cache by default to keep follow-up questions fast and cheap
Compatible with the bring-your-own-key model — you control which Stripe account is queried

What this is not:

Not a write tool. Cannot create products, issue refunds, or cancel subscriptions.
Not Stripe Sigma. No SQL — these are pre-built answers to common founder questions.
Not a Stripe Dashboard replacement. Use it alongside the Dashboard, not instead of it.
Not a marketplace tool. Stripe Connect platforms aren't supported in v1.

Who this is for:

Solo founders and small teams (1–5 people) running SaaS on Stripe who use Claude Code, Cursor, ChatGPT, or another MCP client daily and want to ask questions about their business in natural language without context-switching to the Stripe Dashboard or writing SQL.

Pricing tiers via this hosted listing:

Free: 200 calls per month, never expires
Pro: $14/month for 5,000 calls, $5 per 1,000 overage
Self-host: Free forever via npm — npx stripe-founder-mcp with your own Stripe key

You provide your Stripe key. Your data stays in your Stripe account. Cancel anytime.