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 Langdock?

One person with the right to add connectors in your Langdock 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 Langdock 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.

Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. 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 · Langdock

Stripe in Langdock. In five minutes.

Connect Stripe in Loopthink, paste one URL into Langdock, ask. Hosted in the EU, every call logged.

Start free See the steps

Free for 2 connectors, no card · Pro €19 · EU-hosted

How to connect

Three steps. The third one is asking.

1
Connect Stripe in Loopthink
Restricted API key, read permissions only.
2
Paste one URL into Langdock
Add a custom connector with a name and the URL. That is the whole form.
3
Ask
"Which payouts arrived this week, and what fees were taken?" Every answer comes from your data, every call is logged.

Start free

Show all steps

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.
4
Someone with the permission Create integrations (Editor or Admin by default) opens Integrations → Add integration → Start from scratch → Connect remote MCP.
5
Paste your Loopthink connector URL, choose OAuth 2.0 (Dynamic Client Registration), click Create and connect.
6
Share the integration with users, groups or the whole workspace. Each person signs in to Loopthink once; their calls carry their own name.

Steps checked against the vendor documentation on 17 September 2026: Stripe MCP server · Restricted API keys · Workbench · Langdock: remote MCP servers · Langdock: MCP directory and adding a server · Langdock: workspace permissions

Use cases

What people actually ask Langdock 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?”

Why Loopthink

Stripe has an MCP server. Why Loopthink?

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 runs hosted and gives Langdock a URL. Every colleague signs in with their own account and sees only what you ticked.

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 Langdock?: One person with the right to add connectors in your Langdock 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 Langdock 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 it cost?: Free for one person and two connectors, no card. Pro is €19 a month for up to five people and every connector on the site, with roles, field masking and a 30-day audit. Team is €49 for ten people and adds your own REST APIs and SQL databases, your own domain and your own identity provider. 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.

When colleagues join

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 Langdock user in your team gets exactly this.

Stripe runs on the free tier: two connectors for one person, no card. Roles, a login for every colleague and field masking start at €19 a month with Pro. See the plans