Integrations

Mollie

Connect Mollie to look up payments and customers, create payment links, issue refunds, run subscriptions, and check balances and settlements.

OAuth authorizationFinance & BillingMollie API docsMollie MCP server overview

Nothing is typed into PopMCP. You click Connect Mollie, sign in to Mollie and approve PopMCP, then choose a website profile if your organization has several. There is no developer app, callback URL or key to deal with. If you prefer not to sign in, an API key or advanced access token from Developers, API keys in Mollie can be used under More options instead.

Setup time
1 min
Auth
OAuth authorization
API base URL
https://api.mollie.com/v2

Before you begin

  • A Mollie account. Taking real payments needs Mollie's onboarding to be finished, and test data works before that
  • Your role in Mollie decides what a sign-in can do: you can only approve permissions your role already has
  • Pop-up blockers must allow the Mollie sign-in window to open
  • Only if the AI should create, refund or change anything: an owner or admin in PopMCP to allow write actions

Get your credentials

Start the connection from PopMCP

Open the Mollie connector in PopMCP and click Connect Mollie. There are no fields to fill in: no API key, no developer app and nothing to register.

Sign in to Mollie and approve

The sign-in window opens on my.mollie.com. Sign in if you are not already, read the permissions PopMCP is asking for, and approve. You can only ever approve what your own role in Mollie allows. Your password stays with Mollie.

my.mollie.com/oauth2/authorize
you@example.com

Connect PopMCP to Mollie

PopMCP is asking to use your Mollie organization.

PopMCP would like to
View
Payments, customers, balances and settlements
Manage
Payments, refunds, subscriptions and webhooks
Approve

PopMCP never sees your Mollie password. Asking for a permission here does not let the AI use it: new connections start read-only in PopMCP.

Choose a website profile

Back in PopMCP, pick the website profile this connection should work on, and the workspace to put it in. Payments and customers belong to a profile, so each connection stays on the one you choose. If your organization has one profile, it is the only choice.

app.popmcp.com/connect/accounts
you@example.com
Connectors / Mollie

Choose your website profiles

Each one connects to a workspace.

Website profileWebsiteWorkspace
Acme Shoppfl_QkEhN94Baacme.exampleMain

Prefer a key? Copy one from Mollie

Only if you would rather not sign in, or want a connection that can only touch test data. In Mollie open Developers, then API keys, and create or copy a key. A live_ key reaches live data and a test_ key only test data; either reaches one website profile's payments, customers and subscriptions, but not balances, settlements, invoices or webhooks. For those, create an advanced access token on the same page (only Admins can) and tick its permissions. Mollie shows a secret once, so copy it right away, then paste it in PopMCP under More options and click Connect Mollie.

Open this screen →

my.mollie.com/dashboard/developers/api-access-tokens
you@example.com
Developers / API keys

API keys

Keys are shown once, when they are created.

Website profile: Acme Shop
Live API key
live_dHar...XLSlXsM
Test API key
test_dHar...XLSlXsM
Create API key

To reach balances, settlements and invoices, create an advanced access token instead. It starts with access_.

Check the connection in PopMCP

The Mollie card in PopMCP reads Connected, with the profile name. The everyday tools load at once, and the whole API is one search away. Refunds, charges and every other change wait until an owner or admin allows write actions in PopMCP.

app.popmcp.com/connectors/mollie
you@example.com
Connectors / Mollie

Mollie

Connection
Status
Connected
Website profile
Acme Shop
Access
Read only until write actions are allowed
AreaExample toolAccess
PaymentsWith refunds and chargebacksmollie_payment_overviewRead
MoneyBalance and what is comingmollie_balance_summaryRead
RefundsMoves real moneymollie_refund_paymentWrite

Connect in PopMCP

Open your workspace, choose Mollie in the marketplace, and fill in the connect dialog:

FieldWhat to enter
How you connectpresetClick Connect Mollie, sign in and approve. If your organization has several website profiles, you choose which one next. Your Mollie password is never shared with us.
API key or access token (instead of signing in)secretOnly if you prefer not to sign in. In Mollie go to Developers, API keys, and copy a key, or create an advanced access token. A test_ key only reaches test data. An API key reaches one profile's payments, but not balances, settlements, invoices or webhooks. Mollie shows a key once. Stored encrypted.Encrypted with AES-256-GCM on save and never shown again.

PopMCP verifies the credential against Mollie immediately. On success the connection flips to Verified and its MCP tools are provisioned.

Permissions PopMCP requests

These are the scopes sent to Mollie at authorization time.

ScopeWhy PopMCP asks for it
balance-reports.readRequired by the tools this connector exposes.
balance-transfers.readRequired by the tools this connector exposes.
balance-transfers.writeRequired by the tools this connector exposes.
balances.readRequired by the tools this connector exposes.
business-account-draft-transfers.readRequired by the tools this connector exposes.
business-account-draft-transfers.writeRequired by the tools this connector exposes.
business-account-payee-verifications.writeRequired by the tools this connector exposes.
business-account-transfers.readRequired by the tools this connector exposes.
business-account-transfers.writeRequired by the tools this connector exposes.
business-accounts.readRequired by the tools this connector exposes.
clients.readRequired by the tools this connector exposes.
clients.writeRequired by the tools this connector exposes.
customers.readRequired by the tools this connector exposes.
customers.writeRequired by the tools this connector exposes.
events.readRequired by the tools this connector exposes.
invoices.readRequired by the tools this connector exposes.
mandates.readRequired by the tools this connector exposes.
mandates.writeRequired by the tools this connector exposes.
onboarding.readRequired by the tools this connector exposes.
onboarding.writeRequired by the tools this connector exposes.
orders.readRequired by the tools this connector exposes.
orders.writeRequired by the tools this connector exposes.
organizations.readRequired by the tools this connector exposes.
payment-links.readRequired by the tools this connector exposes.
payment-links.writeRequired by the tools this connector exposes.
payments.readRequired by the tools this connector exposes.
payments.writeRequired by the tools this connector exposes.
payouts.readRequired by the tools this connector exposes.
payouts.writeRequired by the tools this connector exposes.
profiles.readRequired by the tools this connector exposes.
profiles.writeRequired by the tools this connector exposes.
refunds.readRequired by the tools this connector exposes.
refunds.writeRequired by the tools this connector exposes.
sales-invoices.readRequired by the tools this connector exposes.
sales-invoices.writeRequired by the tools this connector exposes.
sessions.readRequired by the tools this connector exposes.
sessions.writeRequired by the tools this connector exposes.
settlements.readRequired by the tools this connector exposes.
shipments.readRequired by the tools this connector exposes.
shipments.writeRequired by the tools this connector exposes.
subscriptions.readRequired by the tools this connector exposes.
subscriptions.writeRequired by the tools this connector exposes.
terminals.readRequired by the tools this connector exposes.
terminals.writeRequired by the tools this connector exposes.
unmatched-credit-transfers.readRequired by the tools this connector exposes.
unmatched-credit-transfers.writeRequired by the tools this connector exposes.
webhooks.readRequired by the tools this connector exposes.
webhooks.writeRequired by the tools this connector exposes.

Verify it worked

The Mollie card in PopMCP shows Connected with the website profile name. Asking the AI for the connection profile (mollie_connection_profile) says whether it is on live or test data, and asking who this connection is (mollie_account_overview) returns your organization and payment methods rather than an authorization error.

Troubleshooting

The sign-in window never opens

Why: A pop-up blocker is stopping the Mollie sign-in window.

Fix: Allow pop-ups for PopMCP in your browser and click Connect Mollie again.

"Mollie did not accept that key"

Why: The key was copied in part, or was removed in Mollie.

Fix: Under Developers, API keys in Mollie, create a new key, since a secret is shown only once, and paste that.

"An API key cannot use this tool"

Why: A live_ or test_ key reaches one website profile's payment data only, and this tool needs organization access, such as balances, settlements or webhooks.

Fix: Reconnect Mollie by signing in, or paste an advanced access token with the permission the message names.

"This connection is missing permission"

Why: The sign-in was not approved for it, your role in Mollie does not allow it, or an access token was made without it.

Fix: Reconnect and approve it, ask an Admin to change your role, or create a token with that permission. mollie_list_permissions shows what the connection has.

A payment the AI should find comes back as not found

Why: It is on the other side: test and live data never mix, and a key reaches only its own website profile.

Fix: On a sign-in, ask for test data. With a key, connect the key for that mode and profile.

"Your Mollie sign-in has ended"

Why: PopMCP's access was removed in Mollie, or the sign-in can no longer be renewed.

Fix: Reconnect Mollie in PopMCP. It takes one click and a sign-in.

Reference

On this page