Does every team member need their own Stripe account?

No. Loopthink holds one key or token for Stripe. Your people sign in to Loopthink with their own identity, and every call to Stripe is logged under their name. Seats in Stripe stay where they are today.

Who has to add the connector in Claude?

One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.

Where does the Stripe key live?

In Loopthink, encrypted, in the EU. It never reaches Claude and never reaches the people using the connector. Rotate it in Stripe whenever you like and paste the new one once.

Can somebody write to Stripe from the chat?

Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.

What does the model see?

The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to Claude. The model gets the numbers, not the people.

Is there an audit trail?

Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.

Free for one person and your own MCP server, forever. Team starts at €99 per month and covers the built connector, per-person identity, roles, masking and audit for the whole team. Prices are on the pricing page, no call needed.

We already run our own MCP server for Stripe. Does it still work?

Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

Stripe · Claude

Connect Stripe to Claude. For your whole team.

Stripe's own MCP server signs in one person with all their Stripe rights, and its write tool covers refunds, payment links and subscriptions. Loopthink holds one restricted read-only key, gives every Claude user in your team their own login, and lets Finance, Support and Management see exactly what their role allows.

Start free Get a demo

Free for your own server · Team from €99 · EU-hosted

The problem

Stripe in a chat client, today.

Today you have two options: give every colleague a Stripe dashboard account, or share one API key with everyone. The first means seats, onboarding and full rights per person. The second means no idea who asked what, and a key that can issue refunds sitting in a chat client.

Who may do what

One matrix for Stripe. Roles across, tools down.

Tool	Finance	Support	Management
Balance & payouts	Finance may use Balance & payouts	Support may not use Balance & payouts	Management may use Balance & payouts
Charges & refunds	Finance may use Charges & refunds	Support may use Charges & refunds	Management may not use Charges & refunds
Invoices	Finance may use Invoices	Support may use Invoices	Management may use Invoices
Customers	Finance may use Customers	Support may use Customers	Management may not use Customers
Disputes	Finance may use Disputes	Support may use Disputes	Management may not use Disputes
Write actions off by default	Finance may not use Write actions	Support may not use Write actions	Management may not use Write actions

Masked for every role: customer email, customer name, card details.

You set this once. Every Claude user in your team gets exactly this.

How to connect

Once on the Stripe side, once in Claude.

On the Stripe side

Restricted API key, read permissions only

1
Stripe Dashboard → Developers → Workbench → API keys → Create restricted key. Or open dashboard.stripe.com/apikeys directly.
2
Set Read on Balance, Charges and Refunds, Customers, Invoices, Payouts and Payment Disputes. Leave every other resource on None; never pick Write.
3
Name the key after Loopthink, confirm with two-factor, copy it once and paste it into Loopthink. Nobody on your team ever sees it.

In Claude

Custom connector, OAuth

1
An Owner opens Organization settings → Connectors → Add and pastes your Loopthink connector URL. On Free, Pro and Max: Customize → Connectors → + → Add custom connector.
2
Each team member opens Customize → Connectors, clicks Connect on Loopthink and signs in once with their own account.
3
In a chat, the + menu lists the connector. Toggle it on, ask away. No key, no config file.

Custom connectors are available on Free, Pro, Max, Team and Enterprise. On Team and Enterprise only Owners can add one; every member still connects individually, which is exactly what gives each call its own identity.

Steps checked against the vendor documentation on 17 September 2026: Stripe MCP server · Restricted API keys · Workbench · Get started with custom connectors using remote MCP · Use connectors to extend Claude's capabilities

Loopthink sits in between: it holds the key, shows Claude a normal login, and applies your roles on every call.

What you get

Four checks between Claude and Stripe.

01
Identify
OIDC/SSO against your own IdP, including Microsoft Entra. The call runs as the person who made it, never as a shared service account.
02
Authorize
Per-role, per-tool, read or write. Anything not explicitly granted never shows up in the tool list in the first place.
03
Mask
Field-level masking and pseudonymization applied on your side, before the result travels. The model never sees the raw field. Composio, AnythingMCP and both provider tunnels have no field-level masking at all.
04
Log
Who asked, which tool, which records, which fields were masked. One audit trail across every AI client, exportable for review.

Use cases

What people actually ask Claude about Stripe.

Finance
“Which payouts arrived this week, and what fees were taken?”
Support
“Show me the last three charges for customer 4711 and whether any were refunded.”
Management
“Refund rate this month versus last month?”

Each question runs as the person who asked it, with that person's role. A Support colleague asking the Finance question gets the tools their own role allows, not an error, not more.

Compare

Four ways to put Stripe into Claude.

	Native Stripe connector	Build it yourself	Enterprise gateways¹	Loopthink
Per-user identity	One personal login, all its rights	Only if you build it	Yes	Yes, every call runs as the person who asked
Tool-level roles	No	Your code	Yes	Yes, write off by default
Field masking	No	Your code	Not documented	Yes, before the model sees the data
Published price	Included in your Stripe plan	Your engineers' time	Contact sales	Free, Team from €99
EU company	Dual HQ, San Francisco and Dublin	Whatever you are	Mostly US	Yes, Germany

Native Stripe connector: Official Stripe MCP with OAuth. One person's rights, read and write through two generic API tools. Refunds need a confirmation click, but they are there.

¹ MintMCP, MCP Manager, Pomerium

Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative

Also for

Connect another system to Claude

All systems and clients →

FAQ

Before you connect.

Does every team member need their own Stripe account?: No. Loopthink holds one key or token for Stripe. Your people sign in to Loopthink with their own identity, and every call to Stripe is logged under their name. Seats in Stripe stay where they are today.
Who has to add the connector in Claude?: One person with the right to add connectors in your Claude workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.
Where does the Stripe key live?: In Loopthink, encrypted, in the EU. It never reaches Claude and never reaches the people using the connector. Rotate it in Stripe whenever you like and paste the new one once.
Can somebody write to Stripe from the chat?: Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.
What does the model see?: The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to Claude. The model gets the numbers, not the people.
Is there an audit trail?: Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.
What does it cost?: Free for one person and your own MCP server, forever. Team starts at €99 per month and covers the built connector, per-person identity, roles, masking and audit for the whole team. Prices are on the pricing page, no call needed.
We already run our own MCP server for Stripe. Does it still work?: Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.

Stripe in Claude, with rules.

One key in Loopthink, one login per person, one matrix that decides who may do what.