Skip to main content
The Qonto CLI (qonto) is a single program for macOS, Linux, and Windows that gives you the Qonto Business API as terminal commands. You sign in once in your browser, and every command after that acts on your Qonto organization as you.
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.
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 before you do.

​
What you can do with it

Read your account

List and filter transactions, statements, attachments, bank accounts, memberships, labels, and teams.

Manage cards

Create cards, lock and unlock them, change limits, options, and restrictions.

Bill clients

Create, finalize, and send client invoices, quotes, and credit notes, and set up payment reminders.

Handle supplier invoices

Upload supplier invoices in bulk, then mark them as paid or reject them.
The full list is in the command reference. 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

macOS and Linux

curl -fsSL https://mcp.qonto.com/cli/install | sh

Windows

irm https://mcp.qonto.com/cli/install.ps1 | iex
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 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 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 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.
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.

​
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 for the details.
Need to report a bug, request a new feature, or didn’t find your answer? Click here.