Mollie MCP server
Mollie in any MCP client, through Memtro: Mollie does not publish this server. Memtro's Mollie connector reads Mollie through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Read Mollie payments, customers, subscriptions and refunds for one website profile. When you ask, can refund a payment or cancel a pending refund, create a payment link, cancel an open payment or a subscription, and create, update or delete a customer. Never creates a payment or a mandate.
Reads
mollie_list_paymentsList Mollie payments, newest first by default: amount, status (open, paid, failed, expired, canceled…), method, description…mollie_list_customersList Mollie customers: name, email, locale, created date.mollie_list_subscriptionsList Mollie subscriptions across all customers: status, amount, interval, next payment date, times remaining.mollie_list_refundsList the refunds made on one Mollie payment: amount, status and date.
Acts, when you ask
These change something in Mollie. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
mollie_create_customerCreates a customer record in Mollie (name, email, locale).mollie_create_refundRefunds a Mollie payment, fully or partly: moves money out of the merchant balance back to the customer, by bank transfer or to their card.mollie_cancel_refundCancels a Mollie refund before it is paid out, which Mollie allows only while its status is queued or pending.mollie_create_payment_linkCreates a Mollie payment link and returns its URL.mollie_cancel_paymentCancels a Mollie payment that is still open, so it can no longer be paid.mollie_cancel_subscriptionCancels a customer's Mollie subscription so no further charges are taken.mollie_update_customerChanges a Mollie customer's name, email or locale; only the fields given are sent.mollie_delete_customerPermanently deletes a Mollie customer, and with it Mollie cancels all the customer's mandates and subscriptions…
Connect it
First connect Mollie on Dashboard → Connections, then add Memtro to your client once. The Mollie tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Mollie connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which payments failed this week?
- › Did the payment from Acme come through?
- › Which subscriptions are active, and when does Brightwave Ltd next pay?
- › Refund 20 euros of Northwind's last payment
- › Cancel Globex's monthly subscription
Questions
- Is this an official Mollie MCP server?
- No. It is Memtro's MCP server with Memtro's Mollie connector behind it: the connector reads Mollie through its API with the credentials you connect on Dashboard → Connections, and Mollie publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Mollie?
- Only when you ask, and only what it has been granted: create a customer record in Mollie; refund a payment, fully or partly, to the customer; cancel a refund that is still queued or pending; create a payment link to share with a payer; cancel a payment that is still open; cancel a customer's subscription so no further charges are taken; change a customer's name, email or locale; delete a customer, cancelling its mandates and subscriptions. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.