> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qonto.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect your AI assistant to your Qonto account

The **Qonto MCP server** lets your AI assistant 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](https://modelcontextprotocol.io/), an open standard created by Anthropic and maintained by the community, that lets large language models discover and call tools exposed by a server. From an end-user point of view, once the server is installed, your assistant gains a new set of capabilities.

<Warning>
  Connecting the Qonto MCP server shares your Qonto account data with a third-party AI tool. **Read the [Terms and Disclosures](/mcp/terms-and-disclosures) carefully before connecting.** When you authorize the connection you accept those terms, including sharing your account data with your chosen AI tool and the lifting of professional secrecy in this regard.
</Warning>

## Endpoint

| Field          | Value                                            |
| -------------- | ------------------------------------------------ |
| Server URL     | `https://mcp.qonto.com/mcp`                      |
| Authentication | OAuth, see [Authentication](/mcp/authentication) |

The server reuses the same identity provider as [`developers.qonto.com`](https://developers.qonto.com). The OAuth scopes documented in the [Business API reference](/get-started/business-api/authentication/oauth/available-scopes) govern what each tool can do on your behalf.

## What you can do with it

Once connected, your assistant can:

<CardGroup cols={2}>
  <Card title="Read your books" icon="magnifying-glass-chart" href="/mcp/capabilities#read-only-insights">
    List and filter transactions, statements, attachments, invoices, quotes, clients, cards, requests, and labels.
  </Card>

  <Card title="Manage cards" icon="credit-card" href="/mcp/tools/cards">
    Create virtual or physical cards, change their status, update limits, and request new ones for teammates.
  </Card>

  <Card title="Bill clients" icon="file-invoice-dollar" href="/mcp/tools/invoices">
    Draft and send client invoices, quotes, and credit notes; mark them as paid; deliver them by email.
  </Card>

  <Card title="Triage requests" icon="check-double" href="/mcp/tools/requests">
    List and create card and multi-transfer requests, decline them, or get a link to approve in the Qonto web app.
  </Card>
</CardGroup>

See [What you can do](/mcp/capabilities) 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.

<CardGroup cols={3}>
  <Card title="Claude Desktop" icon="comments" href="/mcp/install/claude-desktop" />

  <Card title="Claude Code" icon="terminal" href="/mcp/install/claude-code" />

  <Card title="Cursor" icon="code" href="/mcp/install/cursor" />

  <Card title="VS Code" icon="code-branch" href="/mcp/install/vscode" />

  <Card title="ChatGPT" icon="comment-dots" href="/mcp/install/chatgpt" />

  <Card title="Mistral Le Chat" icon="message" href="/mcp/install/mistral" />
</CardGroup>

If you just want the URL and copy-paste instructions, jump to the [Quickstart](/mcp/install/quickstart).

## How it relates to the Business API

The MCP server is built on top of the [Qonto Business API](/get-started/business-api/overview) 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.

<Note>
  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, or onboarding. For those use cases use the [Business API](/api-reference/introduction) directly.
</Note>

## 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](/mcp/security) for the full breakdown.

<Tip>
  Need to report a bug, request a new feature, or didn’t find your answer? [Click here.](https://qonto-developers.zendesk.com/hc/en-001/requests/new)
</Tip>