Skip to main content
The Qonto MCP server lets compatible AI assistants read and act on your Qonto data through a curated set of tools, so you can manage your business banking by chatting with the LLM of your choice. It implements the Model Context Protocol, an open standard maintained by Anthropic, OpenAI, Microsoft, Google, and others, that lets large language models discover and call tools exposed by a remote server. From an end-user point of view, once the server is installed, your assistant gains a new set of capabilities; from a developer point of view, the server is a single HTTPS endpoint that speaks JSON-RPC.

​
Endpoint

FieldValue
Server URLhttps://mcp.qonto.com/mcp
AuthenticationOAuth, see Authentication
The server reuses the same identity provider as developers.qonto.com. The OAuth scopes documented in the Business API reference govern what each tool can do on your behalf.

​
What you can do with it

Once connected, your assistant can:

Read your books

List and filter transactions, statements, attachments, invoices, quotes, clients, cards, requests, and labels.

Manage cards

Create virtual or physical cards, change their status, update limits, and request new ones for teammates.

Bill clients

Draft and send client invoices, quotes, and credit notes; mark them as paid; deliver them by email.

Approve workflows

Triage card and multi-transfer requests, approve or decline them with SCA when required.
See What you can do for the complete capability map and example prompts.

​
Install it

Pick the client that matches your assistant. Cursor and VS Code offer a one-click install; Claude, ChatGPT, and Le Chat take a short paste into their connector settings.

Claude Desktop

Claude Code

Cursor

VS Code

ChatGPT

Mistral Le Chat

If you just want the URL and copy-paste instructions, jump to the Quickstart.

​
How it relates to the Business API

The MCP server is a thin, opinionated layer on top of the Qonto Business API. Each MCP tool maps to one (or, for composite tools like change_card_status, several) Business API endpoints, and every call you make through the MCP server is just a Business API call made on your behalf. You should use the Business API directly if you are building a custom backend integration, an ERP connector, or an embedded product. You should use the MCP server if you want a conversational, ad-hoc interface to your Qonto account through an assistant you already use.
The MCP server only exposes a curated subset of the Business API: read endpoints and a vetted set of write operations. It does not (yet) cover SEPA transfers from a beneficiary, international transfers, webhooks, terminals, payment links, or onboarding. For those use cases use the Business API directly.

​
Security model

  • Every tool call is authenticated as you: the server holds an OAuth access token issued to your Qonto user. It cannot act outside what your role and your organization’s price plan allow.
  • The Qonto MCP server itself does not store conversation content, transcripts, or your business data; it only proxies tool calls to the Business API.
  • The MCP client (Claude, ChatGPT, Cursor, etc.) holds the conversation, including any data the tools return. Review your client vendor’s data handling before connecting.
  • You can revoke access at any time from the connected apps section of your Qonto account.
See Security and limits for the full breakdown.
Need to report a bug, request a new feature, or didn’t find your answer? Click here.