Claude Stripe connectorWhat Claude can do in your Stripe account.
The Claude Stripe connector exposes 11 tools. 7 of them read (your data, balances, analytics, the docs), 1 writes through almost any part of the Stripe API, and 3 are documented nowhere. Below: what Claude can see, what it can change, and which actions Stripe makes you confirm.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach Stripe
Answering a simple question about your payments often means a dashboard filter, an export and a spreadsheet. With the connector, you ask Claude in plain words and it reads your Stripe account through the API, the interface Stripe offers to software, then answers in the conversation. It can also act on the account, which is exactly why the confirmation rules below matter.
Read what happened. stripe_api_read can reach any read method of the Stripe API, so a question about a customer, an invoice or a failed charge gets a direct answer.
Look at the numbers. stripe_analytics queries metrics, analyzes subscriptions and billing and runs financial reports (Stripe flags it as a preview), and get_balance_summary shows your balances in one view.
Plan an integration. stripe_implementation_planner and search_stripe_documentation walk you through Stripe products and docs when you are setting up billing or checkout.
The other side needs care. stripe_api_write can create, update and delete through a very wide part of the API, and Stripe only requires a human confirmation on certain actions, such as refunds and outbound payments. Three tools on the directory sheet appear nowhere in Stripe's own tool table. And nothing runs by itself: no tool fires when a payment succeeds. For event-driven flows, the Stripe n8n integration and the Stripe Make integration do a different job, on a trigger.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and your Stripe account, so Claude can read and act on it while it answers you.
- Tool
- One named thing the connector lets Claude do, like reading data or writing through the API. Claude picks the tools it needs itself.
- Authorization
- Stripe's own consent screen, where you hand Claude the access it uses afterwards. It is granted once, per person, and can be taken back the same way.
- Approval
- The confirmation Claude waits for before something that changes your account. Stripe adds its own for some sensitive actions.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service such as Stripe.
Connect Stripe to Claude in three steps
- 01
Find Stripe in Claude
Open Claude's settings, go to Customize then Connectors, and search for Stripe. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Start the connection
Click Connect and sign in to Stripe in the window Stripe opens. If the link ever breaks, Disconnect and connect again. The access can also be withdrawn from the Stripe side.
- 03
Read the authorization screen
Check Stripe's authorization screen before you accept it. That screen belongs to Stripe, not to Claude, and it sets what the access covers. It can announce broader permissions than what Claude does day to day.
The 11 tools, split by what they do
Stripe gives Claude 11 tools: 7 that read your account, 1 that change something in it, and 3 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 7 read
- 1 write
- 3 not documented
What Claude reads (7)
7 toolsSeven tools that look at your account, your numbers or the documentation and leave everything as it is.
stripe_implementation_planner
Guides you through Stripe's products to accept payments, sell online, set up billing or build an integration, step by step in the chat.
search_stripe_documentation
Looks up Stripe's documentation for an answer to your question, in the language you ask it in.
stripe_api_search
Finds the Stripe API methods that match a keyword, which helps Claude know where your data lives before it reads anything.
stripe_api_details
Returns the detailed parameters of one Stripe API method, so Claude knows exactly what a request expects before it runs it.
stripe_api_read
Reads data with any GET method of the Stripe API, so whatever your account exposes to a read request can come back into the conversation.
get_balance_summary
Displays an interactive summary of your balances across the Stripe balance and Treasury accounts, right in the conversation.
stripe_analytics
Queries metrics, analyzes subscriptions and billing and runs financial reports. Stripe marks it as a preview.
What Claude changes (1)
1 toolOne tool, very broad. Stripe asks for a human confirmation on some of its actions, not all of them.
stripe_api_write
Asks you firstUses any POST, PATCH, PUT or DELETE method of the Stripe API, so Claude can create, update or delete almost anything your permissions allow.
Undocumented (3)
3 toolsThese three names are on the directory sheet but not in Stripe's tool table. No official text says what they do, and we will not guess from a name.
send_stripe_mcp_feedback
No official source describes this tool. The names in Stripe's own tool table differ from those on the directory sheet, and we do not match them by guesswork.
list_available_accounts_or_orgs
Absent from Stripe's tool table, and from any other source we read. The directory gives its name and nothing more, so the page says nothing about what it returns.
manage_stripe_accounts
Listed on the directory sheet with no description in Stripe's documentation or anywhere else. A name is not documentation, so this page makes no claim about its effect on your accounts.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. Stripe adds its own confirmation on top, for some sensitive actions.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time, and they can limit a connector across the organization, for example reading only. Nobody overrides that from a personal account. Claude also works with the rights of the person who connected and nothing more. Stripe's own check covers certain write actions, such as refunds and outbound payments: you open the link Claude gives you and review the request.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, which is a real hole in the catalog.
Anthropic publishes a general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can each connect. No Claude documentation covers this connector: what is known comes from its directory sheet and Stripe's docs. For the current state on your account, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing happens when a payment succeeds, a card fails or a subscription renews.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge in the directory is not a security audit, and Anthropic says on every sheet that it neither picks a publisher's tools nor guarantees their behavior. Stripe adds its own warning: turn on human confirmation of tools and be careful when Stripe runs alongside other connectors, because of prompt injection, text crafted to steer an assistant. For another connector with gaps between its sources, see the Claude gmail connector.
Need help connecting Stripe to Claude?
A person reads every message.
