You can connect Qonto to Claude using the Model Context Protocol (MCP), and once it’s connected, Claude can check a balance, pull up last week’s transactions, or find the status of an invoice without you opening the Qonto dashboard to look it up. This guide covers what Qonto’s MCP server does, both ways to connect it — directly or through a gateway — and why a live business bank account deserves a slower look than most of the tools in this series.

What the Qonto MCP server actually does

Qonto publishes a remote MCP server at mcp.qonto.com/mcp. It exposes your business accounts’ balances, transactions, and invoices as tools Claude can call directly, so prompts like these work against your real Qonto data:

  • “What’s our current balance across all accounts?”
  • “List last week’s transactions over €1,000.”
  • “Find the invoice for this supplier and its status.”
  • “Summarize this month’s spending by category.”

Every prompt in Qonto’s own published examples is a lookup — a balance, a transaction list, an invoice status, a spending summary. None of them describe moving money. That’s a reasonable signal about how the server is meant to be used, but it’s not the same as a guarantee that every tool on the server is read-only; the published use cases describe the intended experience, not a line-by-line audit of the tool list. Before you rely on that distinction, check the actual tools yourself — gate’s free MCP security scanner lists every tool a server exposes, and a quick read of the names and descriptions will tell you whether anything on there can initiate a transfer rather than just report one.

Option 1: Connect Qonto to Claude directly

Claude supports remote MCP servers natively. The short version of the setup:

  • Open Claude’s connector or MCP settings.
  • Add a remote server pointing at Qonto’s MCP endpoint.
  • Sign in with your Qonto account when prompted — standard OAuth, so Claude never sees your Qonto password, and you can revoke access from Qonto’s own account settings at any time.

That’s enough if Claude is the only AI client you use with Qonto. The tradeoff shows up once a second client or a second teammate needs the same access: each one repeats the same OAuth grant, and each grant is its own thing to remember to revoke later.

Option 2: Connect it once, through a gateway

If you’re already juggling more than one MCP server or more than one AI client, wiring each pair directly gets old fast — the connection sprawl covered in what an MCP gateway is. The idea is to connect Qonto (and everything else) to one gateway URL, then point every AI client at that single URL instead of repeating the OAuth step per client.

With gate specifically, connecting Qonto looks like this: add gate’s gateway URL to Claude once, then pick Qonto from the Qonto server page in the directory and sign in with OAuth the same way you would directly. From then on, Qonto’s tools are available in every client connected to your gate URL, with the same per-tool allow, ask, or block rule applied everywhere instead of set up separately in each client. See the full list of servers set up this way on the MCP servers page.

What to check before you connect a bank account

A payments processor holds a slice of your transaction history. A business bank account holds the actual balance, and Qonto’s own examples cover multiple accounts at once — worth a slower look than most connections in this series:

  • Read, or read and write? Confirm what the tool list actually contains before you assume. A tool that reports a balance and a tool that moves money between accounts are not the same risk, and the difference should decide whether a call runs on its own or waits for a person — the same distinction covered in MCP OAuth scopes explained.
  • Which accounts does the grant cover? If your Qonto organization has more than one account — a main account and a separate one for payroll or savings — know whether the connection sees all of them or just one before you ask a broad question like “summarize everything.”
  • Who else on the team can reach it? A shared, revocable connection through one gateway beats every teammate holding their own grant to the company bank account — the access-control question covered in MCP access control for teams.
  • Could a transaction’s own text steer what Claude does next? A transaction description or an invoice line item is content someone else wrote, not data you control — the same untrusted-input pattern covered in the confused deputy problem in MCP. An agent that already has a legitimate banking connection doesn’t need a malicious server to misuse it, just one piece of text it wasn’t expecting to act on.

Troubleshooting the connection

  • OAuth loop or sign-in fails. Make sure you’re signing in with the Qonto member account that actually has access to the organization you want Claude to see, not a personal login for a different business.
  • Claude reports a balance that looks wrong. Check which account the tool is reading from first — a multi-account organization can easily return the wrong one if a prompt doesn’t say which account it means.
  • Tools disappear after a Qonto update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that’s exactly what drift detection is meant to catch — see how MCP rug pulls work for why a one-time review isn’t enough.
Where gate fits: gate connects Qonto once, behind a URL every AI client can share, with allow/ask/block rules you can set per tool — so a balance lookup can run on its own while anything resembling a transfer waits for a person. Every server is scanned for prompt injection before it goes live, and every call goes into a plain-language log, which matters more for a live bank account than for most connections in this series. See the full approach at /mcp-gateway.

The bottom line

Connecting Qonto to Claude with MCP is a normal OAuth flow, direct if it’s your only client or once through a gateway if you want the same access shared across every AI client your team uses. The published use cases all read as lookups — a balance, a transaction list, an invoice status — but don’t take that as a settled fact about the tool list. Check what the connection can actually do before you hand it a broad prompt, and treat a live business bank account with the caution its stakes deserve.