Mollie¶
Artific Connect · Mollie gives a key Mollie's own tools: payments, orders and the rest of what a Mollie account can be asked. It installs from the Marketplace like any other bundle.
What you get¶
One toolset, mollie, holding everything Mollie's own MCP server offers, plus a skill that tells
the model what it cannot do yet and what to confirm before creating a payment.
Signing in¶
The tools act as the person the turn is for, through that person's own Mollie account — so a turn sees exactly the organisation that person is authorised for. Two things follow:
- a request must name a
user; one that names nobody is told so instead of calling a tool; - each person signs in once, from the bundle's page in the console or through the link the model is given the first time it tries.
The consent screen says Artific: the application is this deployment's, registered once by its operator, and no organisation registers one of its own.
Before it works¶
Your administrator has to allow mcp.mollie.com in the key's own egress policy.
If the operator has not registered the Artific application at Mollie yet, the install waits: the bundle sits at needs configuration and names what it is waiting for.
Good to know¶
- Verified 2026-09-24 on
docs.mollie.com/docs/mollie-mcp-server: the server address ishttps://mcp.mollie.com/mcp, and it does not currently support issuing a refund or cancelling a mandate or a subscription — use Mollie's own dashboard for those. - Not verified: the exact scopes an OAuth application needs beyond
profile.read; Mollie's own OAuth reference lists several payment and order scopes without saying which the MCP server itself requires. - The mark: this bundle's card uses Mollie's own mark, from mollie.com/resources, the page Mollie publishes "to help you improve the shopping experience on your website and write about Mollie" (checked 2026-09-24).