Endpoint
| Field | Value |
|---|---|
| Server URL | https://mcp.qonto.com/mcp |
| Authentication | OAuth, see Authentication |
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.
Triage requests
List and create card and multi-transfer requests, decline them, or get a link to approve in the Qonto web app.
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
How it relates to the Business API
The MCP server is built on top of the Qonto Business API and uses its endpoints downstream to act on your behalf. MCP tools are designed around what an assistant needs to accomplish rather than mirroring the API: a single tool may combine several endpoints, add validation, or shape inputs and outputs for conversational use, so there is no one-to-one correspondence between a tool and an API endpoint. 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.