Setup guide
Ask Claude what happened in Stripe this month and get it from the account itself, without exporting a report or handing over a key.
Before you start
Stripe's own connector is in the directory, verified, and it covers payment processing. This page's route is a different shape: the whole Stripe tool list behind one endpoint, with you choosing which of it Claude can touch.
Stripe Verified
Versus
Connecting FloConnector connects Stripe, and Stripe is one of 60 connectors the same endpoint can carry. You do this setup once, not once per app.
Step one
Step two
Control
A profile carries only the tools you switch on, and the endpoint exposes only that profile. That is the whole permission model, and it is set before anyone connects.
Stripe Connected 12/426 8 read 4 write
Tick a row to include it, or flip Read only to lock every write off at once.
FloConnector holds the Stripe credential, encrypted before it is stored, and calls Stripe on the model's behalf. Claude sees the tools and their results, never the credential behind them.
Once it is connected
Each of these runs real Stripe tools, named underneath so you can see what Claude is actually calling. 12 of the 426 tools are covered here.
How much did we take last month, and how does that compare with the month before?
Both months totalled from the payments that actually succeeded, with the fees separated out so the net is the figure that reached your balance.
list_charges list_balance_transactions Which customers are past due, and how much revenue is sitting behind them?
Every subscription Stripe has marked past due, the invoice that failed on each, and the recurring total they add up to.
list_subscriptions search_invoices search_customers Refund Grace Okafor's last payment and tell me what it costs us.
The refund issued against that charge, plus the processing fee, which Stripe keeps when a payment is handed back.
search_customers list_charges create_refund Do we have any open disputes, and when is the evidence due?
Each open dispute with its reason code, amount and evidence deadline, alongside the charge it was raised against.
list_disputes list_charges Set up a payment link for the new onboarding package, billed monthly.
A product, a recurring price and a shareable link, made in that order because Stripe will not hang a price on a product that does not exist yet.
list_products create_product create_price create_payment_link When is our next payout and what is in it?
The pending payout with its expected arrival date, and the charges, refunds and fees that add up to the amount.
list_payouts list_balance_transactions Troubleshooting
Claude Desktop sits on Connect after you signed in
The sign-in has usually succeeded. Check the profile in your dashboard: if the grant is there the connection is live, and restarting the desktop app clears the stale button. It is a client-side issue, not something the server can fix.
The connector saves but no tools appear
Disconnect and reconnect it once. If it is still empty, check in the dashboard that the connection behind the profile is still connected and that you are an assigned member of that profile.
The first load is slow on a very large profile
A profile exposing hundreds of tools takes longer to load, and a model given too many tools chooses worse. Split the work across two profiles rather than exposing everything at once. This is the failure mode most MCP write-ups name and never solve.
No. You authorise on Stripe's own page, and the token that comes back is encrypted before FloConnector stores it. Claude sees the tools and what they return, never the credential behind them.
Only if the refund tool is on the profile. It is one switch, separate from everything that reads, so a profile built for reporting cannot return a payment however the question is phrased.
That is what it is for, and the control is the profile. Start with reads only, check the activity log to see exactly which tools ran, then add the writes you want. Stripe keeps its own record of every API call as well, filed under the connected application.
No. The MCP server is FloConnector's and it is already running. Claude connects to a URL over HTTPS, so there is no package to install and nothing that has to be awake on your laptop for a report to work.
Yes, and this is the reason profiles exist. A support profile can carry the customer lookup and the refund tool and nothing else, while finance gets its own profile and its own URL. People are assigned to profiles one by one.
The endpoint does not change. A profile URL is a standard hosted MCP server, so the same one serves both; only the menu you paste it into is different.
A connection authorises one Stripe account and a workspace holds one connection. Separate accounts for separate brands or countries means a workspace each, with its own endpoint, which is worth deciding before you build the profiles.
Stripe's surface is vast and the toolkit follows it, so there are several near-identical tools for the same job and a few that can change where your payouts land. Switch on the handful you use. A model handed all of them picks worse ones, and an unused tool that can edit an external account is not something you want sitting on a profile.
Stripe returns the brand and the last four digits of a card and nothing beyond that, to anyone, through any tool. Claude can see that a payment failed and on which card; it cannot see the card. That is Stripe's design rather than a setting you can relax.
Your turn
One connection, one endpoint, and 426 Stripe tools your AI can actually run. Start free with 1,000 tool calls and see what your own first week looks like.
