Qonto MCP: connect Qonto to Claude and ChatGPT
Ask Claude or ChatGPT what came in from a customer this week, what you spent on travel last month or which transactions are still missing a receipt. The answer comes straight from your Qonto accounts, without downloading a statement first.
We build the connector for your company on Qonto’s Business API, next to your other systems. It only reads: it never moves money, and your admins decide which groups get it.
Built for your company · Works in Claude, ChatGPT and Copilot
What your team can do with Qonto in Claude and ChatGPT
Cash position without logging in
Receipts before the close
Card spend for your team
Bank data next to the rest
Ask it like this
“Has Boulangeries Moreau paid us this week? Show the incoming transfers.”
“What is our balance across all Qonto accounts right now?”
“Which card transactions from October are still missing a receipt?”
“Summarise our spending last month by cash flow category.”
“What did the cards on Camille Bernard’s team spend on travel this quarter?”
“List all direct debits from the last three months and who they go to.”
What we build for Qonto
Deployed OS has no ready Qonto connector yet. We build it for your company when you start, on Qonto’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.
- Accounts and balances
- Your Qonto accounts and their current balances, for each organisation you connect.
- Transactions
- Incoming and outgoing transactions with counterparty, amount, date, category and whether a receipt is attached.
- Statements
- Monthly account statements, so the AI can find and summarise a period.
- Cards and team members
- Cards and the people they belong to, so card spend can be shown per person or team.
- Cash flow categories
- The categories you use in Qonto, so spend can be grouped the way your company does it.
Who sees what
- Read-only, never moves money
- The connector only reads. It does not create transfers, issue or lock cards or change anything in Qonto. A write action would only be built if your company asks for it and approves it, and payments stay in the Qonto app.
- Access per group, not per Qonto login
- The connector uses one company connection to Qonto’s API, authorised by your Qonto admin with read scopes only, so people do not sign in with their own Qonto login. Deployed OS decides who may use it.
- Your company decides who gets it
- Admins choose which groups get Qonto in Deployed OS, for example finance and management only. A group without access never sees the connector.
- Every call logged
- Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Set up the Qonto connector in three steps
Qonto’s own MCP server or Deployed OS?
Qonto has its own MCP server, on every plan and for every role. Each person signs in with their own Qonto login, the AI only gets what that person’s role allows, and each sign-in covers one organisation. Besides reading transactions and statements it can work on cards, client invoices and transfer requests, while approvals stay in the Qonto app. If the job is one person handling their own Qonto work from Claude or ChatGPT, it is a good fit.
Deployed OS is for when Qonto is one system among several. It puts Qonto next to your accounting system, CRM and other tools in one company connection, can cover several organisations, admins decide which groups get each system, every call is logged in one place, and the same rules apply in Claude and ChatGPT. We can also add company-specific tools on top, such as a weekly cash summary across all your accounts.
Qonto MCP: common questions
Yes. Qonto has its own hosted MCP server, on every plan, where each person signs in with their own Qonto login and each sign-in covers one organisation. Deployed OS adds Qonto to one company connection with your other systems, read-only, with access per group and one log.
No. The connector we build only reads accounts, transactions, statements and cards. It does not create transfers or touch cards, and payments are always made and approved in the Qonto app.
No. The connector uses one read-only company connection to Qonto’s API. Who may use it is decided per group in Deployed OS, and every call is logged.
Yes. We connect each organisation you choose, so the AI can answer across them, and you decide which groups see which organisation.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Qonto data is fetched when someone asks for it.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.