> ## 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.

# Multi-organization

> Read across several Qonto organizations with a single connection

If you belong to several Qonto organizations, the **multi-organization endpoint** lets one MCP connection span all of them. You authorize once, ticking every organization you want to share, and your assistant can then read data from any of them in the same conversation.

Two things differ from the standard server: tools on this endpoint are **read-only**, and every organization-scoped tool takes a required `organization_id` argument that says which organization a call targets.

<Warning>
  Connecting the multi-organization endpoint shares the data of **every organization you select** with your chosen AI tool. **Read the [Terms and Disclosures](/mcp/terms-and-disclosures) carefully before connecting.**
</Warning>

## Endpoint

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

This endpoint is independent of the single-organization server at `https://mcp.qonto.com/mcp`: you can configure both in the same client side by side, and connecting or revoking one does not affect the other.

## How authorization works

The first time you connect an MCP client to `https://mcp.qonto.com/multi-organization/mcp`:

1. Your browser opens at Qonto.
2. You sign in if you are not already. The consent screen lists the organizations you are a member of, with a checkbox per organization: tick the ones you want to share.
3. You review the requested permissions and confirm.
4. The client stores the resulting authorization locally and the Qonto tools become available in your chat.

From the client's point of view this is standard OAuth; there is nothing extra to configure beyond the URL.

To add or remove organizations later, disconnect and reconnect, ticking the organizations you want. Revoking from the **connected apps** section of your Qonto account withdraws access to all selected organizations at once.

## Targeting an organization

Every organization-scoped tool on this endpoint takes a required `organization_id` argument (a UUID) naming the organization the call targets. In practice you never type it: the assistant calls `list_user_organizations` first, matches the company name you mentioned, and threads the id through subsequent calls.

Two tools take no `organization_id`, because neither is bound to an organization: `list_user_organizations` (it is what tells you the ids) and `get_qonto_public_pricing` (Qonto's public price list).

| Tool                      | What it does                                                                                                                                                                   | Upstream                                                                                                               |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| `list_user_organizations` | Lists the organizations you consented to: id, name, legal name, legal number and country, and your role in each. The starting point for every multi-organization conversation. | [Retrieve user organizations](/api-reference/business-api/accounts-organizations/organizations/get-user-organizations) |

<Note>
  Only organizations selected at consent time are available on this connection. Calls naming any other organization are rejected, even if you are a member of it. Re-authorize to extend your selection.
</Note>

`list_user_organizations` exists only on this endpoint; the single-organization server does not expose it.

**Try it**

> Which of my organizations can you see?
>
> Compare last month's spend across my two companies.
>
> List unpaid client invoices in each of my organizations.

## Read-only tool surface

The endpoint exposes the reading tools behind [Read-only insights](/mcp/capabilities#read-only-insights), per organization: transactions and statements, cards, clients, invoices, quotes and credit notes, payment links, requests, memberships, teams, labels, cash flow categories, products, the organization itself and its plan, plus `list_user_organizations` and Qonto's public price list.

Write operations (creating cards or invoices, changing statuses, submitting requests, uploading attachments) are **not** available here. Use the single-organization server at `https://mcp.qonto.com/mcp` for those.

One read tool is deliberately kept off this endpoint: `get_card_iframe_url`. What it returns is not data but a short-lived credential that displays full PAN and CVV, so it stays on the single-organization server.

<Note>
  Since nothing on this endpoint mutates your account, Strong Customer Authentication is never triggered here.
</Note>

See the [Tool reference](/mcp/tools/overview) for per-tool detail; the read tools from those pages apply on this endpoint, each with the extra `organization_id` argument.

## Client configuration

MCP clients that support remote HTTP servers accept the same shape, keyed so it can coexist with the single-organization entry:

```json theme={null}
{
  "mcpServers": {
    "qonto-multi-org": {
      "type": "http",
      "url": "https://mcp.qonto.com/multi-organization/mcp"
    }
  }
}
```

Wherever a per-client guide under [Install](/mcp/install/quickstart) asks you to paste the server URL, paste this one instead. Installs that go through a directory entry rather than a URL (the Qonto connector in Claude, the one-click **Add to Cursor** button) always point at the single-organization server, so for this endpoint use your client's **custom connector** or **add server by URL** path.

<Note>
  Because both endpoints share the host `mcp.qonto.com`, this one advertises its own authorization server one level down, at `/.well-known/oauth-authorization-server/multi-organization`. Clients that follow the OAuth metadata pointer returned by the server ([RFC 9728](https://datatracker.ietf.org/doc/html/rfc9728) and [RFC 8414](https://datatracker.ietf.org/doc/html/rfc8414)) find it on their own. A client that only probes the root `/.well-known` paths ends up authorizing against the single-organization server, and its tools then arrive without `organization_id`, which is how you recognise the case.
</Note>

## Choosing an endpoint

|            | Single organization             | Multi-organization                                          |
| ---------- | ------------------------------- | ----------------------------------------------------------- |
| Server URL | `https://mcp.qonto.com/mcp`     | `https://mcp.qonto.com/multi-organization/mcp`              |
| Consent    | One organization per connection | Several organizations in one authorization                  |
| Tools      | Read and vetted write tools     | Read-only, organization-scoped tools take `organization_id` |

For the shared security posture, data handling, and rate limits, see [Security and limits](/mcp/security).