Mollie MCP Server

What it does

Mollie runs this server itself at https://mcp.mollie.com/mcp; there is nothing to install. An MCP client connects to that address, the user signs in on Mollie's own login page and approves the connection, and from then on the assistant can work with that Mollie account in plain language instead of through the Mollie web app.

It covers most of the day-to-day merchant API: looking up, searching and totalling payments and creating new ones; creating payment links and seeing who paid them; listing, creating, charging and updating customers; creating, changing and cancelling subscriptions; viewing, creating and revoking mandates; capturing authorised payments; reading balances, balance reports and transactions; listing settlements and the payments, refunds, chargebacks and captures inside them; creating and updating sales invoices; reading the invoices Mollie bills the merchant; checking active payment methods; listing point-of-sale terminals and website profiles; and creating, updating and testing webhooks.

What the assistant may do is bounded by the signed-in user's role in the Mollie organisation: the connection never grants more than that role already has, and every action is recorded in the account under that user, as if they had done it in the Dashboard. Any member of the organisation can connect, not only owners or admins.

Two things the docs page states that are easy to miss: refunds can be seen inside settlements but cannot be issued through the server, and the earlier static-token way of connecting has been deprecated, so OAuth sign-in is now the only supported route (docs.mollie.com, Mollie MCP Server, updated 2026-09-30). Mollie does not publish a list of tool names, and the server has no entry in the official MCP registry.

What it needs

A Mollie account (as any member of the organisation) whose role allows the actions you want. An MCP client that supports remote servers with OAuth sign-in through Client ID Metadata Documents, such as Claude, ChatGPT or Cursor. Clients that only run local stdio servers need the separate mcp-remote proxy run with npx, which needs Node.js and opens a browser for the Mollie sign-in.

Limits

It cannot issue refunds; refunds only appear as part of settlement contents. Mollie's docs list capabilities by area but give no tool names or count. Static access tokens are deprecated; only OAuth sign-in is supported. There is no page in the Mollie web app to see or revoke connected AI tools: access is removed from within the client's own connected-apps settings. It is hosted only; there is no package or source to run yourself.

Who it suits

Merchants and finance or support staff who already use Mollie and want to check payments, balances and settlements, or handle customers, subscriptions, payment links and invoices, from an assistant without opening the Dashboard. Because it is official, hosted and signs in with the user's own role, it suits teams that want actions attributed to a named person. It does not suit anyone who needs to issue refunds, wants to self-host or audit the server code, or needs a fixed, documented tool list; developers building their own Mollie product are pointed by Mollie to its Agent toolkit library instead.