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

> The Qonto Business API from your terminal, for you and your AI agents

The **Qonto CLI** (`qonto`) is a single program for macOS, Linux, and Windows that gives you the [Qonto Business API](/get-started/business-api/overview) as terminal commands. You sign in once in your browser, and every command after that acts on your Qonto organization as you.

```bash theme={null}
curl -fsSL https://mcp.qonto.com/cli/install | sh
qonto auth login
qonto transactions list --status completed --side debit
```

Output is a readable table when you run a command yourself, and JSON when the output goes to a script, a pipe, or an AI agent. The same command works for all three.

<Warning>
  If you let an AI agent run `qonto` for you (Claude Code, Cursor, Codex, and so on), everything the CLI prints goes into that agent's conversation and is sent to its provider. Read [Using the CLI with AI agents](/cli/ai-agents) before you do.
</Warning>

## What you can do with it

<CardGroup cols={2}>
  <Card title="Read your account" icon="magnifying-glass-chart" href="/cli/commands/transactions-and-statements">
    List and filter transactions, statements, attachments, bank accounts, memberships, labels, and teams.
  </Card>

  <Card title="Manage cards" icon="credit-card" href="/cli/commands/cards">
    Create cards, lock and unlock them, change limits, options, and restrictions.
  </Card>

  <Card title="Bill clients" icon="file-invoice-dollar" href="/cli/commands/invoicing">
    Create, finalize, and send client invoices, quotes, and credit notes, and set up payment reminders.
  </Card>

  <Card title="Handle supplier invoices" icon="file-import" href="/cli/commands/supplier-invoices">
    Upload supplier invoices in bulk, then mark them as paid or reject them.
  </Card>
</CardGroup>

The full list is in the [command reference](/cli/commands/overview). Every command also documents itself: `--help` on any command shows the API endpoint it calls, the OAuth scope it needs, and every flag.

## Install it

<CardGroup cols={2}>
  <Card title="macOS and Linux" icon="apple" href="/cli/install#macos-and-linux">
    `curl -fsSL https://mcp.qonto.com/cli/install | sh`
  </Card>

  <Card title="Windows" icon="windows" href="/cli/install#windows">
    `irm https://mcp.qonto.com/cli/install.ps1 | iex`
  </Card>
</CardGroup>

Both installers check the download against its published SHA-256 before installing anything. On macOS the program is signed with Qonto's Apple Developer ID and notarized by Apple. See [Install](/cli/install) for other options (a specific version, another directory, `.deb`, `.rpm`, and `.apk` packages).

## How it relates to the Business API and the MCP server

Each CLI command calls **one** Business API endpoint. The flags come from that endpoint's parameters, and the output is the endpoint's JSON response, unchanged. If you know the API, you already know the CLI; the [API reference](/api-reference/introduction) describes every field.

Use the **CLI** when you want to work with your Qonto data from a terminal: quick lookups, shell scripts, scheduled exports, or an AI coding agent that already runs commands on your machine.

Use the **[MCP server](/mcp/overview)** when you want to chat with an assistant such as Claude or ChatGPT, which calls Qonto tools designed for conversations.

Use the **Business API directly** when you are building a product: a backend integration, an ERP connector, or an embedded experience.

<Note>
  The CLI covers a vetted subset of the Business API. It **cannot make payments**: there is no command for SEPA, internal, or international transfers, beneficiaries, or approving requests. It can create a transfer request, which a teammate then approves in Qonto. See [Security](/cli/security#what-the-cli-cannot-do).
</Note>

## Security model

* Every command is **authenticated as you**, with an OAuth token issued to your Qonto user. It can never do more than your role and your organization's plan allow.
* The session is stored in your operating system's **credential store** (macOS Keychain, Windows Credential Manager, or a Secret Service on Linux), never in a plain file unless you explicitly ask for it.
* The CLI is a **public OAuth client**: there is no API key or client secret to copy, and none is hidden in the program.
* You can revoke the CLI's access at any time from the **connected apps** section of your Qonto account, or with `qonto auth logout`.

See [Security](/cli/security) for the details.

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