Connect Stripe to Claude Code
Stripe in Claude Code
Claude Code reads the Stripe data of one Adrails workspace through the MCP server, from the terminal, in the project you are working in. It reads customers, charges and refunds, subscriptions and prices, through a restricted key that has read permissions only. Nothing writes back to Stripe, and each figure keeps its source and currency, so a Stripe figure sits next to Meta Ads spend without being mixed into it.
Reviewed Oct 4, 2026
Stripe tools
What Claude Code can ask Adrails about Stripe
| Tool | What it returns | Example question |
|---|---|---|
| saas_performance | Active subscriptions, trials, normalized MRR, ARR, collected payments and refunds over a period, with customer and subscription counts by billing cadence, each source and currency kept separate | How many active subscriptions and trials do we have, and what is MRR this month? |
| store_customers | Customers imported from Stripe, newest first: name, email domain, country, creation date and lifetime spend, with no full email address | Who signed up last week, from which countries, and what do they pay? |
| business_review | A check of a calculation you state, such as a payback estimate, where every number must quote a tool result or your own words from this connection's history | Check the payback estimate I wrote against the MRR and spend figures in this conversation. |
| integrations_status | What the workspace has connected, what each source can do and how fresh each of its data streams is | When were payments and subscriptions last read from Stripe? |
From the Adrails MCP tools reference and the Stripe integration documentation on 4 October 2026.
01
What Claude Code reads from Stripe
Stripe is connected once in Adrails, under Integrations, with a restricted key Stripe creates with the read permissions already selected, pasted once in Adrails. Adrails reads customers, charges and refunds, subscriptions and prices, through a restricted key that has read permissions only, and Claude Code reaches the same data through the MCP server, with your sign-in and inside the one workspace you chose.
In Claude Code, the Stripe reads come from 4 tools: saas_performance, store_customers, business_review and integrations_status. The table above says what each one returns and gives a question to type as it is. Every result comes back twice, as exact data for the model and as a readable table for you, so a figure Claude Code states can be traced to the call that produced it.
02
Connect Claude Code
Claude Code adds remote MCP servers from the command line. By default the server is added for the current project only; --scope user adds it for every project, and --scope project writes it to a .mcp.json file at the project root that your team can share through version control. If the browser does not open for the sign-in, copy the address Claude Code prints and open it yourself.
Every client uses the same server URL, https://adrails.ai/api/mcp, and the same sign-in: Claude Code registers itself, you sign in to Adrails, then choose the workspace and the permissions on the consent screen. Stripe needs nothing on the Claude Code side, since it is already connected in that workspace under Integrations.
- 1. From your project directory, run claude mcp add --transport http adrails https://adrails.ai/api/mcp
- 2. In Claude Code, run /mcp, select adrails and authenticate
- 3. Your browser opens Adrails: sign in, choose the workspace and the permissions, and choose Allow access
- 4. Return to Claude Code and ask your first question
03
Three questions to start with
Ask in your own words: Claude Code picks the tool, Adrails returns the figures, and Claude Code's model does the reasoning, so a tool call uses no agent credit. Each result carries the exact data in structuredContent.result and the same figures as readable tables.
A result is at most 256,000 bytes, so a long history is asked for in shorter ranges or pages. saas_performance, store_customers, business_review and integrations_status are the tools Claude Code reaches for; the table above shows what each returns.
- How many active subscriptions and trials do we have, and what is MRR this month?
- Which countries did last week's new customers come from, and what do they pay?
- Check my payback estimate against the MRR and ad spend figures in this conversation.
04
What stays out of reach
No tool writes to Stripe. The restricted key is read-only: Adrails never charges, refunds or changes anything in Stripe. The write permissions the consent screen can offer concern ad accounts, integrations, automations, Knowledge and campaign drafts, and none of them reaches Stripe.
Each source and currency stays separate in every result: a Stripe figure is never added to a Shopify or Meta Ads one, never converted, and always named with its source, so Claude Code can set them side by side but cannot blur them into one total.
A read covers the whole workspace, every ad account and integration it has, and never another workspace. Full customer email addresses are not stored, so Claude Code sees a name, an email domain and a country.
05
Permissions, cadence and limits
Read workspace data, the one permission every connection needs, covers every integration of the workspace, Stripe included. No write permission exists for Stripe, so a member and an owner read the same data, and Claude Code lists no tool that could change it.
Payments are read every 15 minutes, subscriptions every 30 minutes and customers every hour. Adrails' own billing also runs on Stripe, but it is separate from this connection.
Calls on one connection run one at a time, at most 60 a minute per access token, and a connection works in the one workspace you chose at consent: to work in another, connect Claude Code again and choose it. Revoke Claude Code under Your connections on the MCP page in Adrails; removing the server in Claude Code does not revoke it there.
Go further
Read more
- Claude Code integrationClaude Code with Adrails: setup, the 63 tools and the controls, for every source of the workspace.
- Stripe in AdrailsThe Stripe connector: the restricted key, the charges, refunds and subscriptions it reads, and what it never does.
- Connect an AI clientEvery client, step by step, then how to check the connection.
- MCP tools referenceEvery tool, its inputs and who can call it.
FAQ
Common questions
Does Claude Code need an API key for Stripe?
No. Stripe is connected once in Adrails, under Integrations, with a restricted key Stripe creates with the read permissions already selected, pasted once in Adrails. Claude Code signs in to Adrails with OAuth, with no client ID or secret to copy, and tool results never contain provider credentials or Adrails tokens.
Can Claude Code change my Stripe data?
No. The restricted key is read-only: Adrails never charges, refunds or changes anything in Stripe. Claude Code may still ask for your permission in the terminal before a tool call; that governs the call, and the call only reads.
How fresh is the Stripe data?
Payments are read every 15 minutes, subscriptions every 30 minutes and customers every hour. integrations_status returns how fresh each data stream is, so Claude Code can check the last read before quoting a figure.
Can I connect several Stripe accounts?
A Claude Code connection reads every integration of the workspace it was given, and saas_performance keeps each source and currency separate. To read another workspace's Stripe data, connect Claude Code again and choose that workspace.