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

# What you can do

> Concrete capabilities the Qonto MCP server gives your assistant

The Qonto MCP server exposes a curated set of tools grouped by business domain. Each tool maps to one or more endpoints of the [Business API](/api-reference/introduction), and each call is authenticated as you, the consenting user. This page is a high-level map; for a full per-tool reference, see [Tool reference](/mcp/tools/overview).

## Read-only insights

Anything you can see in the Qonto app, your assistant can read through MCP:

* **Transactions and statements**, list, filter, retrieve transactions; pull monthly statements with presigned download URLs.
* **Cards**, list cards, view metadata, fetch the iframe URL for displaying full PAN/CVV to you.
* **Clients**, list, look up, and inspect clients.
* **Invoices, quotes, credit notes**, list and retrieve client invoices, supplier invoices, quotes, and credit notes.
* **Payment links**, list the organization's payment links; read one together with the payments collected against it.
* **Requests**, see pending card requests and multi-transfer requests.
* **Memberships, teams, labels**, discover who is in the organization, the team structure, and the label taxonomy used for transaction tagging.
* **Organization**, the authenticated organization's metadata (legal name, IBANs, slug).

Typical prompts:

> Show me all transactions over €1,000 last month with no attachment.
>
> Which clients have not paid us in the last 60 days?
>
> List my pending requests grouped by requester.
>
> What labels do we use, and which ones are children of "Travel"?

## Day-to-day operations

The MCP server can also act on your account, within what your role and OAuth scopes allow:

* **Cards**, create virtual or physical cards, lock and unlock, mark as lost or stolen, discard.
* **Card requests**, create or decline a card request on behalf of a teammate. Approving is done by the approver in the Qonto web app; the assistant returns a link to the approve page.
* **Multi-transfer requests**, bundle several outgoing transfers into one request that an approver can sign with SCA.
* **Client invoices**, create, update, finalize, mark as paid or unpaid, send by email, delete drafts.
* **Quotes**, create, update, send, delete drafts.
* **Credit notes**, issue a credit note linked to an existing client invoice.
* **Supplier invoices**, change status (mark paid, unmark paid, reject).
* **Payment links**, create a shareable checkout page from a basket of items or an existing client invoice.
* **Products**, create and list the products that appear on client invoices and quotes.
* **Clients**, create, update, delete clients in your address book.
* **Memberships and teams**, invite new members (employee or reporting), create teams.

Typical prompts:

> Issue a €1,200 + VAT invoice to ACME for "Consulting June 2026".
>
> Create a virtual card called "Ads" for me with a €500 monthly limit, restricted to online payments.
>
> Give me the link to approve the pending card requests from the design team.
>
> Mark supplier invoice INV-3382 as paid.

<Warning>
  Write operations always go through Qonto's standard approval logic. Approving a request happens in the Qonto web app, not through the assistant. Mutations that need SCA (e.g. some card creations) prompt you in the Qonto mobile app, your assistant will tell you to approve and continue.
</Warning>

## Reporting and analysis

Because LLMs are good at slicing data once it is in context, the MCP server is at its best when used for reporting:

> Compare this month's spend vs last month, broken down by label.
>
> Which suppliers are taking the longest to bill us?
>
> Plot my cash inflows for Q1 by client.
>
> Forecast next month's outflows based on the recurring outgoing transactions.

The assistant pulls the underlying data via `list_transactions`, `list_supplier_invoices`, and friends, and then runs the analysis in its own conversation.

## What it does **not** do

The MCP tool surface is deliberately narrower than the full Business API. The server does **not** expose:

* **SEPA outgoing transfers** to a beneficiary (use the Business API or the Qonto app).
* **International transfers** (Business API only).
* **SEPA direct debit** mandates, subscriptions, collections.
* **Webhooks** (subscriptions, deliveries, signatures).
* **Terminals**.
* **Payment link deactivation** and **provider connections** (creating, listing, and reading payment links is supported, see [Payment links](/mcp/tools/payment-links)).
* **Onboarding** (creating a new Qonto organization).
* **Embed Auth Links** and **encoded requests**.

For any of those, head to the [Business API reference](/api-reference/introduction).

## Example prompts library

For a deeper set of starter prompts grouped by domain, jump to the [tools overview](/mcp/tools/overview), every domain page lists prompts that exercise the tools in it.