To connect Stripe to Claude, authorize your account at onboard.windsor.ai/app/stripe, then add the Windsor.ai connector in Claude. That’s it. Open a new chat and ask about your revenue.
Here’s the problem it solves: Stripe holds the ground truth on revenue, but that data stays locked inside the Stripe dashboard, one report at a time.
Checking monthly recurring revenue means one view. Checking churn means another. Neither view tells you whether the customers you’re losing are the ones your ad spend is targeting, or whether the deals your CRM marks “closed won” are the ones actually paying on time.
Blending Stripe with the rest of your stack today usually means exporting a CSV from Stripe, exporting again from your CRM or ad platform, then reconciling everything by hand in a spreadsheet, a process that’s slow and goes stale the moment new transactions come in.
Connecting Stripe to Claude through Windsor MCP removes that step. Claude gets direct, structured access to your Stripe data, so you can ask about revenue, churn, refunds, and customer value in plain language, and combine it with any other connected source in the same conversation.
2 steps to connect Stripe to Claude
Setting up the Stripe to Claude integration takes about a minute and requires no code.
📖 Official documentation: How to integrate data into Claude with Windsor MCP.
Prerequisites
- A Windsor.ai account (free or paid plan)
- A Stripe account with API access
- A Claude account
Step 1. Connect Stripe to Windsor
Go to onboard.windsor.ai/app/stripe and select Stripe as your data source. Authorize the connection with your Stripe API key or via OAuth, whichever your account supports. No passwords are shared with or stored by Windsor.
Step 2. Add the Windsor.ai connector in Claude
In Claude, open the Windsor.ai connector page and click Connect.
Quick tip: Set permissions to “Always allow”. Your Stripe data then stays available in every new Claude conversation without reconnecting.
Once both steps are done, confirm the connection works with a simple prompt:
List my connected Stripe accounts and show total revenue and new customers for the last 30 days.
If Claude returns real numbers from your account, the Stripe to Claude integration is live and ready for deeper analysis.
The metrics that matter for Stripe
Windsor gives Claude access to Stripe’s full data model, covering charges, invoices, subscriptions, refunds, payouts, and customers. Some of the fields used most often in analysis:
| Metric | What it tells you |
Transaction amount (amount) |
Amount of each individual charge or payment. |
Transaction fee (fee) |
The fee Stripe deducts from each transaction. |
Net amount (net) |
What you actually receive after fees are deducted. |
Currency (currency) |
The currency a transaction was processed in. |
Invoice amount due (invoice__amount_due) |
How much is still owed on an invoice. |
Invoice amount paid (invoice__amount_paid) |
How much has already been paid on an invoice. |
Subscription status (subscription__status) |
Whether a subscription is active, trialing, past due, or canceled. |
Subscription period end (subscription__current_period_end) |
When the current billing period ends and the next charge is due. |
Refund amount (refund__amount) |
How much was refunded to a customer. |
Payout amount (payout__amount) |
How much Stripe transferred to your bank account. |
What to ask Claude about your Stripe data: prompt ideas
Below are practical prompt ideas that cover the questions Stripe’s own dashboard doesn’t answer directly.
MRR and revenue trend
Prompt idea:
Using Stripe subscription and invoice data, calculate monthly recurring revenue for each of the last 12 months. Show the month-over-month growth rate and flag any month where MRR declined.
Churn analysis
Prompt idea:
Using Stripe subscription data, list all subscriptions canceled in the last 90 days along with the cancellation reason where available. Calculate the churn rate for each of the last 3 months and note whether it is trending up or down.
Failed payments and dunning
Prompt idea:
Using Stripe invoice data, list all invoices with a past due or unpaid status, including the customer, amount due, and how many days overdue each one is. Which customers are at the highest risk of involuntary churn?
Revenue by plan or product
Prompt idea:
Using Stripe subscription item and product data, break down total recurring revenue by product and plan for the current month. Which plan contributes the most revenue, and which has the most active subscribers?
From closed deal to live subscription
The intro asked whether the deals your CRM marks “closed won” are the ones actually paying. Windsor MCP lets Claude close that gap itself, because the Stripe connector writes as well as reads.
Two actions are available:
-
Create a customer from an email or a name, returning the Stripe
cus_id. - Create a subscription for that customer at a fixed amount and interval, which is exactly the shape of a contract value coming out of a CRM.
So a deal that closed this morning becomes recurring revenue in one message:
Our CRM shows a closed-won deal with Harborview for 450 EUR per month, contact [email protected]. Create the Stripe customer and start the monthly subscription.
Everything else in Stripe stays untouched. Claude cannot create a charge, issue a refund, move a payout, change a price, or cancel a subscription, and it shows you the customer and subscription details before creating either. The current list of actions is in the write actions documentation.
Bonus: analyze Stripe alongside your full marketing stack
Windsor connects Stripe alongside 350+ other sources, so payment data can sit in the same conversation as your store, your books, or your ad accounts.
- Stripe + Shopify: Reconcile Stripe payouts against store orders to catch missing or mismatched transactions.
- Stripe + QuickBooks: Tie payment data to your books for a real read on profitability, not just revenue.
- Stripe + Google Ads: Connect ad spend to actual revenue collected, not just platform-reported conversions.
Conclusion
Stripe already holds the answers to most of the revenue questions that matter: what’s recurring, what’s churning, what’s overdue, and what a customer is actually worth. The problem has never been the data. It’s the gap between what Stripe’s dashboard shows and the questions a business actually needs answered.
Connecting Stripe to Claude through Windsor MCP closes that gap. Ask about MRR, churn, failed payments, or revenue by plan in plain language, and get an answer built from live Stripe data instead of a stale export.
And when the question needs context beyond Stripe, your store, your books, or your ad accounts, Windsor connects those too, in the same conversation. When the answer calls for a new customer or a new subscription, Claude can set those up without you switching tabs.
🚀 Connect Stripe to Claude with Windsor MCP in under a minute. Get started for free.
FAQs
Is it secure to connect Stripe to Claude?
Yes. Windsor authorizes Stripe using an API key or OAuth, and your Stripe credentials are never shared with or stored by Claude. Reporting never alters your figures, and the only two write actions are creating a customer and starting a subscription, both confirmed with you first. Nothing can move money, so charges, refunds, payouts and price changes stay inside Stripe.
Can I combine Stripe with other data sources?
Yes. Windsor supports 350+ connectors, and you can have several active in the same Claude conversation. Common combinations include Stripe with your CRM to connect closed deals to actual payments, Stripe with your e-commerce platform to reconcile payouts against orders, and Stripe with your ad platforms to calculate true return on ad spend.
Can Claude create charges or issue refunds in Stripe?
No. Claude can create a customer and start a recurring subscription, which is useful when a closed deal needs to become live revenue. It cannot create charges, issue refunds, move payouts, change prices, or cancel subscriptions. Those actions stay inside Stripe, made by you.
How current is the Stripe data Claude sees?
Windsor pulls data through the Stripe API, so each time you ask Claude a question it can reflect your most recent transactions, invoices, and subscription changes rather than a static export from days or weeks earlier.
Windsor vs Coupler.io

