Skip to main content
The Qonto MCP server authenticates clients with OAuth. The same consent screen you see when connecting a third-party app to Qonto is reused for MCP clients, so there is no API key or organization ID to copy by hand.

​
Who can connect

Connecting an MCP client authorizes a third-party app on your Qonto organization, so who may do it follows Qonto’s rules for connected apps: If your role is not allowed to use Qonto MCP, the OAuth flow still completes and your client reports a healthy connection, but your assistant lists no Qonto tools and every tool call is refused with a message asking you to have an owner or an admin enable MCP access for your role. See Troubleshooting. Being allowed to connect does not widen what you can do. Once connected, every tool call is still bound by your role, see Security and limits.

​
Enabling Qonto MCP for managers and employees

Owners and admins can extend Qonto MCP to the rest of the organization. The setting is per organization: it applies to every manager and employee in the organization you are signed into, and it changes nothing for owners, admins, and accountants, who can connect either way.
1

Open Qonto AI

Sign in to the Qonto web app and open Qonto AI from the left sidebar.
2

Find the Qonto MCP panel

On that page, find the Qonto MCP panel and the Enable for managers and employees card.
3

Turn access on

Switch Give managers and employees access to Qonto MCP on.
Switching it back off revokes the same way. Managers and employees keep their client configuration and their consent, but their Qonto tools stop working until access is granted again. Either way, changes take a couple of minutes to take effect, so ask people to retry rather than to reinstall.
Only owners and admins see the Qonto MCP panel. If you are a manager or an employee you cannot enable it yourself, ask an owner or an admin of your organization.

​
What you will see

The first time you connect an MCP client (Claude, Cursor, ChatGPT, Le Chat, …) to https://mcp.qonto.com/mcp:
  1. Your browser opens at Qonto.
  2. You sign in if you are not already, pick the organization to connect, and review the permissions the client is asking for.
  3. You confirm. The client stores the resulting authorization locally and reconnects to the MCP server.
  4. The Qonto tools become available in your chat.
From then on, the client keeps the connection alive on its own. You do not need to copy anything between Qonto and the client.
On the multi-organization endpoint (https://mcp.qonto.com/multi-organization/mcp), step 2 shows a multi-select list instead: you tick every organization you want the assistant to access, and a single authorization covers them all.

​
What it can do on your behalf

The MCP server acts as you:
  • It cannot exceed what your role and your organization’s price plan allow.
  • It is bound to the permissions you granted at consent time. To grant more, you have to re-authorize.
  • Sensitive operations (PSD2-classified actions like creating certain cards) still require Strong Customer Authentication in the Qonto mobile app. The MCP server cannot bypass SCA, when one of these is triggered, your assistant will ask you to approve in the app and continue once you have.
The permissions catalog is the same as for the Business API: see Available OAuth scopes for the full list.

​
Reviewing and revoking access

Active connections are listed in the connected apps section of your Qonto account. From there you can revoke a connection at any time; the MCP client can no longer reach Qonto until you grant consent again. Removing the server from your MCP client (Claude, Cursor, …) cleans up the client side. Revoking the consent inside Qonto cleans up the server side. Doing both is the safest way to fully disconnect.

​
Sandbox vs production

The public Qonto MCP server (https://mcp.qonto.com/mcp) targets the production Qonto environment. A separate sandbox deployment is intended for partner development; reach out to your Qonto contact if you need access.