Connect Stripe MCP to your AI Agents

Ask your Stripe data anything. MRR, churn, refunds — answered in plain English.

Example prompts

Everything you can ask your agent about your Stripe data.

Ask in plain English — Sequel translates it into a Stripe query, runs it, and your agent hands back the answer. No SQL, no dashboards, no CSV exports.

Connect to your agent
What you can ask your agent
  • What's our MRR for May, broken down by plan?
  • How many customers churned last month?
  • Show me the top 10 customers by lifetime revenue.
  • What were our Stripe fees in Q1?
  • List failed payment intents in the last 7 days with the failure reason.

Install

Install Stripe MCP in your agent

Pick your app and Sequel installs itself: a one-click link where the client supports it, that client’s own few steps where it doesn’t. Every route signs in with your Sequel account over OAuth, so there is no API key to copy and nothing to keep in sync.

Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Grok, Muse, dots and any other MCP app

Already have an MCP client?

https://api.sequel.sh/mcp

Add it as a remote (streamable HTTP) server and sign in when prompted. Skills come with it; nothing else to install. Manual setup per client

Choose your app

  • Claude

    One click, opens in the app

  • Cursor

    One click, opens in the app

  • VS Code

    One click, opens in the app

  • ChatGPT

    Turn on developer mode, then add Sequel. About two minutes.

  • Claude Code

    Run one command, then sign in with /mcp.

  • Codex

    Run one command, then sign in.

  • Gemini CLI

    Run one command, then sign in with /mcp auth.

  • Grok

    Add Sequel as a connector and sign in.

  • Grok Bot

    Paste this to the bot. It registers Sequel and asks you to sign in.

  • Muse

    Muse writes its own connector. One message is the whole setup.

  • dots

    Add Sequel in ChatGPT; your dot picks it up with no extra step.

  • OpenCode

    Add Sequel as a remote server from the OpenCode CLI.

  • Other MCP app

    Any client that speaks remote MCP can connect with this URL.

Skills

Playbooks that run on Stripe

Step-by-step procedures your agent follows on your Stripe data, instead of improvising a query. Browse all skills

Can we trust our product metrics

Two tools show different numbers for the same metric and nobody knows which to trust. Reconciles the disputed figure against a system of record such as Stripe or the application database, then finds the instrumentation defect behind it: duplicate and near-duplicate event names, events that silently stopped firing, missing properties and system-fired events counted as user actions.

Dispute and refund risk monitor

Track chargeback and dispute activity and refund rate against the Visa VAMP and Mastercard ECM thresholds that get a payment account fined or shut off, and find which products, plans or cohorts generate them. Covers dispute rate versus dispute activity, per-network denominators and dispute-fighting economics.

Failed payment and involuntary churn audit

Separate customers who chose to leave from cards that simply declined: failed payments, declined renewals and involuntary churn, and where in the dunning and retry sequence the recovery is being lost. Covers involuntary churn share, first-attempt failure rate, payment recovery rate, decline codes and which accounts are sitting in dunning right now.

Feature launch impact readout

Measure whether a feature we just shipped actually landed: adoption against an eligible denominator of users who could even reach it, breadth, depth and sustained use after the release, a pre and post impact estimate with or without a control group, and a keep, iterate or sunset call.

Find our activation moment

Discover the aha moment: which early in-product action, taken in the first session or first week, most separates users who stay from users who vanish, how to score candidate first actions by retention lift, and what share of new signups ever reach it. Covers activation metric definition, activation rate and time to value.

Is our retention curve flattening

Do users keep coming back, or do they drift away after the first week or month? Builds the cohort retention curve for your key action at its natural frequency and judges whether it flattens to a plateau or decays to zero, covering N-day versus unbounded retention, repeat usage, leaky bucket diagnosis and how the plateau compares to published benchmarks.

Frequently asked questions

How do I connect Stripe to Sequel?

Create a Restricted Key in your Stripe Dashboard with read-only permissions on the resources you want Sequel to query (customers, charges, invoices, subscriptions, etc.), paste it into Sequel's Stripe connector, and click Test. The whole process takes under a minute.

Should I use a Secret Key or a Restricted Key?

Always prefer a Restricted Key. It lets you scope access exactly to the resources Sequel needs (read-only), and you can revoke or rotate it from the Stripe Dashboard at any time without affecting the rest of your integrations.

Does Sequel use Stripe Connect / OAuth?

No. Stripe Connect OAuth is designed for platforms that act on behalf of merchants — marketplaces, billing-on-behalf-of, etc. Sequel reads your own Stripe data, where a Restricted Key is the simpler, narrower grant.

Can Sequel make changes to my Stripe account?

No. The Stripe connector ships only read tools (list customers, list charges, get balance, search, etc.) and you should pair it with a read-only Restricted Key for defense in depth.

Can I query both test and live Stripe data?

Yes. Create two separate connections — one with a test-mode key (rk_test_…) and one with a live-mode key (rk_live_…). Sequel keeps them isolated, and the connection name makes it obvious which is which.

Does Sequel store my Stripe data?

No. Sequel queries the Stripe API at the moment you ask a question and discards the results once they're shown to you. Only your Restricted Key is stored, encrypted at rest with AES-256-GCM.

Can I combine Stripe with other data sources?

Yes. Connect Stripe alongside Postgres, BigQuery, Google Analytics, or any other Sequel source and ask cross-source questions — like 'Show me MRR from Stripe alongside signups from Postgres by week'.

How fresh is the data?

It's live. Each query hits the Stripe API directly, so what you see is what Stripe has right now. The balance ledger and account events update within seconds of the underlying transaction.

What about Stripe Sigma — do I still need it?

Sigma is great for ad-hoc SQL if you already know SQL and the Stripe schema. Sequel replaces the parts of that workflow you don't enjoy: writing the SQL, remembering the column names, and waiting for the editor — you just ask a question.

Start analyzing your Stripe data today

Connect in minutes — then ask across all your data, not just one source.