FinanceConnector
Stripe
Read Stripe customers, invoices, subscriptions and balance, manage catalog and payment links, in Claude or ChatGPT via Tulina's own MCP server — never a refund.
Official site: stripe.com
What it can do
4 read/2 write
- 01Read
Read charges, invoices and subscription state
- 02Read
Read customers and their payment history
- 03Read
Total what was invoiced over a period, per currency
- 04Read
Read the balance, payouts and the fees and net of each transaction
- 05Write
Manage products, prices, coupons, promotion codes and payment links
- 06Write
Add invoice items and create draft invoices, never sent
Read access is the useful half here. A reporting workflow wants last month's revenue and which subscriptions moved, not the ability to issue a refund, and a connector that cannot charge anyone is a connector nobody has to think twice about.
Does Stripe have an MCP server?
Yes. Stripe hosts an official MCP server at https://mcp.stripe.com,
with tools that read through any listed GET method of its API, write
through its POST, PATCH and DELETE methods, and search Stripe's
documentation. Tulina reaches Stripe through its own MCP server, with a
deliberately smaller write surface, on the same link as the rest of the
company's tools.
How do you connect Stripe to Claude and ChatGPT?
Through Tulina's own MCP server, not Stripe's own hosted one, which can also issue refunds. From the same chat as Claude or ChatGPT, read customers, invoices, subscriptions, payment history and balance, and manage the product catalog, draft invoices and payment links. The methods to refund a charge, cancel a subscription or move money do not exist in this connector.
- In the Stripe Dashboard, open Developers, then API keys, and create a restricted key. Read permissions cover every question on this page; catalogue and payment-link writes need the matching write scopes.
- Paste it into Tulina's Stripe connector. A test key reads the test world and a live key the live one: the mode comes from the key.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in. The MCP page has the link.
If you bill for several companies from one platform account, the connector also takes a Connect account id, and every read then targets that account.
Can I use the Stripe MCP with Claude?
Yes, either one. Stripe lists its own connector in Claude's directory and a plugin for ChatGPT, signed in with OAuth. Tulina's connector works in both through the single Tulina link, alongside HubSpot, Pennylane and the other systems a finance question tends to need.
Tulina vs Stripe's official MCP server
| Stripe's MCP server | Tulina | |
|---|---|---|
| Endpoint | mcp.stripe.com, hosted by Stripe | mcp.tulina.ai/mcp, one link for every connected tool |
| Sign-in | OAuth, or an agent API key | A restricted or secret key held in Tulina's vault, for a person or the organisation |
| Refunds, cancellations, finalising or voiding an invoice | Reachable through its write tool; Stripe asks a human to confirm some actions, such as refunds | Absent from the connector |
| Writes it allows | Most of the API methods it lists, including subscriptions | Customers, invoice items, draft invoices, the catalogue and payment links |
| Searches Stripe's documentation | Yes | No |
| In the same conversation | Stripe | Stripe plus your CRM, accounting and product analytics |
Stripe's server is the right tool for building or operating a Stripe integration. Tulina's is built for the person reading the numbers, who should never be one prompt away from a refund.
What you can ask it
"How much did we invoice last month, and how much did we collect?" The agent totals the month's invoices server-side, grouped by currency, and says whether the sweep was complete. It then reads balance transactions for the same window, where each line carries its fee and its net. The two figures answer different questions and are reported side by side.
"Which subscriptions are about to leave?" Stripe has no churning
status, so the agent builds one: active subscriptions set to cancel at
period end, and those past_due or unpaid. For the failing ones it
reads the customer's payment methods, where an expired card usually
explains the problem.
"Make a payment link for the annual plan, usable once." The agent lists prices to find the right one and creates a link that deactivates after its first payment. The page is hosted by Stripe, no card number passes through Tulina, and nobody is charged until a person pays.
Draft the monthly investor update and Expand accounts from usage both read Stripe this way.
What the Stripe connector can't do
- Refund, cancel a subscription, finalise, send or collect an invoice, transfer money, close a dispute or delete a customer. The methods are not in the underlying library, so no configuration turns them on. Do them in the Stripe Dashboard.
- Change a price's amount. Stripe prices are immutable: a new price is created and the old one deactivated.
- Look back further than 30 days in the event feed, which is Stripe's retention. A quarter is read from invoices and payments instead.
- Add amounts across currencies. Every total stays per currency, in the currency's smallest unit.
- Search beyond the seven resources Stripe's search covers, and an object created a minute ago may not appear in search yet.
- Total more than 2,000 invoices in one sweep. Past that it says the sum is incomplete, and the window is narrowed.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Stripe once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Stripe at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Stripe returns something usable instead of something generic.
Processes that run on Stripe
Draft the monthly investor update
Revenue, pipeline, the plan's own targets, and last month's commitments are pulled together into a draft with the numbers already in it.
5 steps →Expand accounts from usage
Each morning, accounts near a plan limit or on a feature their plan lacks get an offer priced on your packaging rules, an expansion deal and a drafted proposal.
7 steps →Turn signups into pipeline
PQL scoring for every trial signup: enriched, scored on your ICP, the first session read, a play chosen by your rules and a deal opened for the right rep.
7 steps →
