Mollie MCP: connect Mollie to Claude and ChatGPT
Ask Claude or ChatGPT which payments failed yesterday, what is in this week’s settlement or which chargebacks came in this month. The answer comes straight from Mollie, without downloading a settlement report first.
We build the connector for your company on Mollie’s own API, next to your shop, accounting and support systems. It only reads by default, and your admins decide which groups get it.
Built for your company · Works in Claude, ChatGPT and Copilot
What your team can do with Mollie in Claude and ChatGPT
Settlements matched without a spreadsheet
Payments by method and status
Answer “where is my refund?”
Chargebacks before they pile up
Ask it like this
“Which payments failed or expired yesterday, by payment method?”
“What is in our latest settlement, and how much of it is refunds and chargebacks?”
“Has the refund for Lotte Jansen’s order from last week been processed?”
“How many chargebacks did we get in October compared with September?”
“Which iDEAL payments from Bakkerij Verbeek are still open?”
“Summarise this month’s refunds by reason in the description.”
What we build for Mollie
Deployed OS has no ready Mollie connector yet. We build it for your company when you start, on Mollie’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.
- Payments
- Payments with their method, status, amount and description, filtered the way you ask.
- Refunds
- Refunds on each payment and their status. Issuing a refund we only build if your company asks for it.
- Chargebacks
- Chargebacks with the payment behind each one, so disputes can be followed up.
- Settlements
- Settlements, the payouts to your bank account, with the payments, refunds, captures and chargebacks in each one.
- Customers
- Customers in Mollie and their payments, so the AI can say who paid what.
Who sees what
- Read-only by default
- The connector reads. It does not create payments, issue refunds or change anything in Mollie. If your company wants the AI to issue refunds, we build that as a separate action you give to the groups that should have it.
- Access per group, not per Mollie login
- For a company’s own integration we use an organisation access token, which a Mollie admin creates under Developers in the Mollie web app. So people do not sign in with their own Mollie login; Deployed OS decides who may use it.
- Your company decides who gets it
- Admins choose which groups get Mollie in Deployed OS, for example finance and customer service. A group without access never sees the connector.
- Every call logged
- Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Set up the Mollie connector in three steps
Mollie’s own MCP server or Deployed OS?
Mollie has its own MCP server. You sign in on Mollie’s login screen, and it gets no permissions beyond the ones you already have in Mollie. It looks up payments, creates payments and payment links, manages customers and shows settlements with their refunds, chargebacks and captures. It does not issue refunds at the moment. Mollie names Claude, ChatGPT and Cursor as clients. If the job is one person working with Mollie from their AI tool, it is a good fit.
Deployed OS is for when Mollie is one system among several, or you want something it does not do. It sits next to your shop, accounting and support tools in one company connection, admins decide which groups get each system, every call is logged in one place, and the same rules apply in Claude and ChatGPT. If you need it, we build the actions your team is missing, such as issuing a refund for customer service with your own limits.
Mollie MCP: common questions
Yes. Mollie has its own MCP server, where each person signs in with their Mollie account and keeps their own permissions. It reads payments, settlements, refunds and chargebacks, creates payments and payment links, and does not issue refunds at the moment. Deployed OS adds Mollie to one company connection with your other systems, with access per group and one log.
Not by default. The connector we build reads payments, refunds, chargebacks and settlements. If your company wants refunds issued from Claude or ChatGPT, we build that action on Mollie’s API and you decide which groups get it.
No. A company’s own integration uses an organisation access token that a Mollie admin creates. Who may use it is decided per group in Deployed OS, and every call is logged.
It can read what each settlement contains, so the AI can line it up with your accounting system when that is connected in Deployed OS too. It does not post anything to your books.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Mollie data is fetched when someone asks for it.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.