Skip to main content
The Qonto MCP server speaks the standard Model Context Protocol over streamable HTTP. Most clients only need two things: the server URL and OAuth authorization.

​
Server URL

https://mcp.qonto.com/mcp

​
Generic configuration

Any MCP client that supports remote HTTP servers accepts the same shape: 
{
  "mcpServers": {
    "qonto": {
      "type": "http",
      "url": "https://mcp.qonto.com/mcp"
    }
  }
}
The client will open the OAuth flow on first connection and store the resulting token. No client secret, no API key, no organisation ID to copy by hand.

​
Per-client guides

Claude Desktop

Paste the URL into Claude connectors and finish the OAuth handshake.

Claude Code

One CLI command, then /mcp to authenticate.

Cursor

Click the deeplink and Cursor adds the server in one click.

VS Code

Click the deeplink to register the server with GitHub Copilot Chat.

ChatGPT

Add as a Custom Connector via Developer Mode.

Mistral Le Chat

Add as a Custom MCP Connector under Intelligence.

​
What happens on first connection

  1. The client sends a JSON-RPC initialize to https://mcp.qonto.com/mcp and discovers that the server requires OAuth.
  2. The client opens your browser at the Qonto authorization endpoint.
  3. You sign in to Qonto, pick the organization to connect, and consent to the requested scopes.
  4. You are redirected back to the client with an access token; the client stores it locally.
  5. The client re-issues initialize, then tools/list, and the Qonto tools become available in chat.
The server is stateless and does not pin a session to a particular pod, so first-time and subsequent connections behave identically, there is nothing to keep alive between requests.

​
Already connected and need to reset?

  • Revoke the connection on Qonto’s side: the connected apps section of your Qonto account.
  • Remove the server from your MCP client following the per-client guide.
  • Reinstall following any of the install guides above. A fresh OAuth flow will run.

​
Troubleshooting

If initialize fails, the tool list is empty, or the OAuth window will not close cleanly, see Troubleshooting.