bunq MCP server: connect AI agents to bunq from the EU

bunq is a Dutch bank based in Amsterdam, licensed by De Nederlandsche Bank and used by private customers and businesses across Europe. Its public API covers accounts, payments and cards. bunq itself provides an MCP server for its developer documentation only, so assistants can answer API questions.

The community server bunq-mcp-server (ErfanMomeniii/bunq-mcp on GitHub), MIT licensed and published on npm, connects agents to account data. It handles bunq's RSA key setup, device registration and sessions automatically, runs over stdio and offers 14 tools, eleven of them read-only.

A freelancer can ask what came in this month, which card payments went to software subscriptions, and how much is left on the tax savings account. A small team can have an agent check whether a customer's transfer has arrived before shipping an order.

With writes enabled, the agent can send a payment request to a client by email for an unpaid invoice, or prepare a draft payment to a supplier. The draft then waits in the bunq app until you approve it there, so the agent cannot complete it alone.

In the bunq app, open your profile, then Security and settings, Developers, API keys, and create a key. It is shown only once. On inference.eu, add the bunq connector to an agent and paste the key; it is stored encrypted in the EU.

Try the bunq sandbox first: it gives test accounts with fake money, so you can check every tool before connecting your real account. The server stores its session context with owner-only file permissions and never logs the key.

The server talks directly to the bunq API and signs every request, so account and transaction data goes between your agent and bunq, a Dutch bank, as it does in the bunq app. No other provider sits in between.

On inference.eu, the model that reads your transactions runs in EU data centres, and your API key is stored encrypted in the EU. Transactions reveal counterparties, spending and sometimes health or political information, so restrict this connector to agents that truly need it.

The riskiest tool is bunq_create_payment, which sends money immediately and cannot be reversed. The server marks write tools as destructive so clients ask for confirmation. For most workflows, prefer bunq_create_draft_payment, which also needs your approval in the bunq app.

On inference.eu, require a person to approve every write call, and consider leaving instant payments out of the agent entirely. A bunq API key has broad rights, so use a separate key per agent and revoke it in the bunq app when no longer needed.