qontoctl
qontoctl is a CLI and MCP server for the Qonto banking API, enabling AI assistants and users to manage nearly all aspects of a Qonto business account.
Accounts: List, create, update, close bank accounts; download IBAN certificates and bank statements.
Transactions: List, search, filter transactions; manage attachments (list, add, remove).
Cards: List, create (individual or bulk up to 50), lock/unlock, report lost/stolen, discard; update limits, nickname, options (ATM, NFC, online, foreign), and restrictions; get secure iframe URL for card details (PAN, CVV, expiry); list available designs.
SEPA Transfers: List, create, cancel transfers; download proof PDFs; verify payees (single and bulk).
Internal & Bulk Transfers: Create internal transfers between accounts; list, view, and create bulk transfers.
Recurring Transfers: Create, cancel, list, and view recurring transfers.
International Transfers: Check eligibility, list supported currencies, create quotes, manage international beneficiaries (list, add, update, remove), and create international transfers.
SEPA Beneficiaries: List, add, update, trust/untrust beneficiaries.
Clients & Invoicing: Full lifecycle for client invoices (create, update, finalize, send, mark paid, cancel); manage quotes (create, update, delete, send); list credit notes; manage clients (list, create, update, delete).
Supplier Invoices & E-Invoicing: List, view, bulk-create supplier invoices; retrieve e-invoicing settings.
Payment Links: List, create, deactivate payment links; list payments and available methods; manage provider connection.
Memberships & Organization: List memberships, show current user, invite members; retrieve organization details.
Requests: List, approve, decline organization requests; create flash card and virtual card requests.
Insurance: Show, create, update insurance contracts; upload/remove documents.
Attachments & Labels: Upload/show attachments; list/show labels.
SCA Sessions: View session status; mock SCA decisions (sandbox only).
Authentication: Configure OAuth2 and API key profiles; manage login, refresh, revoke, and profile lifecycle.
MCP Integration: Exposes all operations as MCP tools for AI assistants (Claude, Cursor, Windsurf) with natural language interaction.
Allows for the management of SEPA beneficiaries and transfers, enabling actions such as listing, adding, and trusting beneficiaries, as well as creating, canceling, and downloading proofs for SEPA transfers.

CLI and MCP server for the Qonto banking API.
This project is brought to you by Alexey Pelykh.
Unofficial project. QontoCtl is independent and not affiliated with, endorsed by, or supported by Qonto. See the Disclaimer.
What It Does
QontoCtl lets AI assistants (Claude, etc.) interact with Qonto through the Model Context Protocol. It can:
Organizations — retrieve organization details and settings
Accounts — list, create, update, close bank accounts; download IBAN certificates
Transactions — list, search, filter bank transactions; manage transaction attachments
Bank Statements — list, view, and download bank statements
Labels — manage transaction labels and categories
Memberships — view team members, show current membership, invite new members
SEPA Beneficiaries — list, add, update, trust/untrust SEPA beneficiaries
SEPA Transfers — list, create, cancel transfers; download proofs; verify payees
Internal Transfers — create transfers between accounts in the same organization
Bulk Transfers — list, view, and create bulk SEPA transfer batches
Recurring Transfers — list, view, create, cancel recurring transfers
International Transfers (SWIFT) — create SWIFT transfers and manage international beneficiaries
Cards — list, create, update, lock/unlock, report lost/stolen, discard cards
Teams — list and create teams
Webhooks — create and manage webhook subscriptions
Payment Links — create, deactivate, and manage Stripe-backed payment links
Insurance — show, create, update insurance contracts and manage documents
Terminals (POS) — list Qonto Terminals and initiate terminal payments
Products — list catalogue products
Clients — list, create, update, delete clients
Client Invoices — full lifecycle: create, update, finalize, send, mark paid, cancel, upload files
Quotes — create, update, delete, send quotes
Credit Notes — list and view credit notes
Supplier Invoices — list, view, and bulk-create supplier invoices
Requests — list organization requests
Attachments — upload and view attachments
E-Invoicing — retrieve e-invoicing settings
Related MCP server: Seline MCP
QontoCtl and Qonto's official MCP
QontoCtl is an independent, unofficial project — not affiliated with or endorsed by Qonto.
Qonto ships its own official MCP server — hosted, free on every plan, and installable in a tap from Claude, ChatGPT, Cursor, and more. If you want to talk to your finances — "show my balances", "chart last month's spending", "draft an invoice" — it's an excellent, well-made option.
QontoCtl is built for a different job: automating Qonto, not just chatting with it.
The official MCP is a hosted assistant you log into as a user. QontoCtl is a local, open-source toolkit — a CLI, an MCP server, and a library — that runs on your own machine with your own credentials, including as a headless service account.
Official MCP | QontoCtl | |
Runs headless — CI, cron, scripts, no chat | Interactive only | ✅ CLI + MCP + library |
Authentication | OAuth, per-user | ✅ API key (service account) or OAuth |
Executes SEPA / internal / recurring transfers | Prepares approval requests | ✅ Yes, with SCA handled* |
API coverage | Curated subset | ✅ Comprehensive |
Self-hosted · your credentials · open source | Qonto-hosted | ✅ AGPL-3.0, local-first |
Comparison based on Qonto's public MCP documentation as of July 2026.
* Transfers to untrusted payees still require your Strong Customer Authentication approval, as they must. QontoCtl handles the SCA continuation so scripted flows — to trusted beneficiaries and between your own accounts — complete without a human at the terminal.
QontoCtl also supports multiple Qonto organizations from one setup via named profiles — handy for accountants, holding companies, and anyone running the books for several entities.
The official MCP talks to Qonto. QontoCtl automates it. Many people will use both — the official MCP in a chat window, QontoCtl in a pipeline.
Prerequisites
Node.js >= 24
A Qonto business account with API access
Installation
npm install -g qontoctlOr run directly with npx:
npx qontoctl --helpOr install via Homebrew:
brew install qontoctl/tap/qontoctlQuick Start
# 1. Install
npm install -g qontoctl
# 2. Create a profile with your Qonto API credentials
qontoctl profile add mycompany
# 3. Test the connection
qontoctl profile test --profile mycompany
# 4. List your accounts
qontoctl account list --profile mycompanyMCP Integration
QontoCtl implements the Model Context Protocol (MCP), letting AI assistants interact with your Qonto account through natural language.
MCP Client Configuration
Add to your Claude Desktop configuration (claude_desktop_config.json):
{
"mcpServers": {
"qontoctl": {
"command": "npx",
"args": ["qontoctl", "mcp"]
}
}
}claude mcp add qontoctl -- npx qontoctl mcpAdd to .cursor/mcp.json in your project root:
{
"mcpServers": {
"qontoctl": {
"command": "npx",
"args": ["qontoctl", "mcp"]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"qontoctl": {
"command": "npx",
"args": ["qontoctl", "mcp"]
}
}
}Pointing MCP at a non-default config file
The MCP server has no CLI flags. To load credentials from a config file other than ~/.qontoctl.yaml, set QONTOCTL_CONFIG_FILE in the host's env block:
{
"mcpServers": {
"qontoctl": {
"command": "npx",
"args": ["qontoctl", "mcp"],
"env": {
"QONTOCTL_CONFIG_FILE": "/abs/path/to/qontoctl.yaml",
},
},
},
}The path is captured at server startup. See docs/configuration.md for the full resolution chain.
Available MCP Tools
Tool | Description |
Organization | |
| Show organization details including name, slug, and bank accounts |
Accounts | |
| List all bank accounts for the organization |
| Show details of a specific bank account |
| Download IBAN certificate PDF for a bank account |
| Create a new bank account |
| Update an existing bank account |
| Close a bank account |
Transactions | |
| List transactions for a bank account with optional filters |
| Show details of a specific transaction |
| List attachments for a transaction |
| Attach a file to a transaction |
| Remove attachment(s) from a transaction |
Statements | |
| List bank statements with optional filters |
| Show details of a specific bank statement |
Labels | |
| List all labels in the organization |
| Show details of a specific label |
Memberships | |
| List all memberships in the organization |
| Show the current authenticated user's membership |
| Invite a new member to the organization |
SEPA Beneficiaries | |
| List SEPA beneficiaries in the organization |
| Show details of a specific SEPA beneficiary |
| Create a new SEPA beneficiary |
| Update an existing SEPA beneficiary |
| Trust one or more SEPA beneficiaries |
| Untrust one or more SEPA beneficiaries |
SEPA Transfers | |
| List SEPA transfers with optional filters |
| Show details of a specific SEPA transfer |
| Create a SEPA transfer |
| Cancel a pending SEPA transfer |
| Download SEPA transfer proof PDF |
| Verify a payee (Verification of Payee / VoP) |
| Bulk verify payees (VoP) |
Internal Transfers | |
| Create an internal transfer between two bank accounts |
Bulk Transfers | |
| List bulk transfers |
| Show details of a specific bulk transfer |
| Create a bulk SEPA transfer (auto-resolves VoP via bulk_verify_payee) |
Recurring Transfers | |
| List recurring transfers |
| Show details of a specific recurring transfer |
Terminals (POS) | |
| List Qonto Terminals linked to the organization |
| Initiate a payment on a terminal (returns 202 Accepted) |
Products | |
| List catalogue products with optional pagination and sort |
Clients | |
| List clients with optional pagination |
| Show details of a specific client |
| Create a new client |
| Update an existing client |
| Delete a client |
Client Invoices | |
| List client invoices with optional filters |
| Show details of a specific client invoice |
| Create a draft client invoice with client and line items |
| Update a draft client invoice |
| Delete a draft client invoice |
| Finalize a client invoice (assign number) |
| Send a client invoice to the client via email |
| Mark a client invoice as paid |
| Unmark a client invoice paid status |
| Cancel a finalized client invoice |
| Upload a file to a client invoice |
| Show upload details for a client invoice |
Quotes | |
| List quotes with optional filters |
| Show details of a specific quote |
| Create a new quote with client and line items |
| Update an existing quote |
| Delete a quote |
| Send a quote to the client via email |
Credit Notes | |
| List credit notes in the organization |
| Show details of a specific credit note |
Supplier Invoices | |
| List supplier invoices with optional filters |
| Show details of a specific supplier invoice |
| Create supplier invoices by uploading files |
Requests | |
| List all requests in the organization |
SCA Sessions | |
| Show the status of an SCA session ( |
| Simulate an SCA decision in the Qonto sandbox (sandbox-only) |
Attachments | |
| Upload an attachment file (PDF, JPEG, PNG) |
| Show details of a specific attachment |
E-Invoicing | |
| Retrieve e-invoicing settings for the organization |
Example Prompts
Once configured, you can ask your AI assistant things like:
"Show my Qonto account balances"
"List recent transactions over 1000 EUR"
"What were last month's card payments?"
"Show all team members in my organization"
"List bank statements for January 2026"
"Create a summary of this week's debits"
SCA Continuation
Some Qonto write operations — creating a transfer, modifying a card, approving a request — require Strong Customer Authentication (SCA): the user has to approve the request in the Qonto mobile app before it executes. QontoCtl wraps every SCA-gated MCP write tool with a continuation flow so the LLM client never has to reimplement polling.
How a wrapped write tool behaves
When an SCA-gated tool (e.g. transfer_create, card_create, beneficiary_trust, request_approve) hits a 428 SCA challenge, the wrapper polls the SCA session inline. If the user approves within the polling window, the tool returns the operation's success result transparently — the LLM never sees the SCA round-trip. If polling times out (or polling is disabled), the tool returns a structured SCA-pending response carrying the session token and instructions to continue.
Every wrapped tool exposes two optional input fields for this flow:
wait— maximum seconds to poll inline before falling back to the pending response.sca_session_token— bind a previously approved SCA challenge to a retry.
The wait knob
Value | Behavior |
| Poll for up to 30 seconds, then fall back to the structured pending response. |
| Poll for the specified number of seconds (capped at 120). |
| Skip polling entirely. Return the SCA-pending response immediately on the first 428. |
The 120 upper bound is the hard ceiling enforced via Zod at the input boundary. The practical ceiling is your MCP host's request timeout — Claude Desktop hardcodes ≈ 60 s and Cursor's effective limit is ≈ 30 s, so values above those will surface as host-side timeouts before the wrapper resolves. Use a small wait (e.g. 5-10) when the LLM expects the user to be present and willing to approve immediately. Use wait: false (or wait: 0) for pure two-step flows where the LLM and the user converse out-of-band between the SCA challenge and the retry.
Two-step fallback (out-of-band continuation)
When polling does not resolve, the SCA-pending response carries:
A user-facing message:
"SCA required. The user must approve this operation on their Qonto mobile app."A
Session token: <token>line (token validity: 15 minutes from issuance).Step-by-step instructions to continue.
The LLM (or the user) can then:
Poll session status with the
sca_session_showtool, passing the captured token. It returnswaiting,allow, ordeny.Retry the original tool once the status is
allow, passing the same parameters plussca_session_token: "<token>". The wrapper invokes the operation exactly once with the token bound — no second poll happens.
PSD2 dynamic linking. The SCA session token is bound to the original request parameters (amount, payee). Reusing a token against a different operation is rejected by Qonto. Reissue an SCA challenge by calling the original tool again whenever the parameters need to change.
Caller-supplied retry (sca_session_token)
When sca_session_token is set on a wrapped write tool, the wrapper:
Invokes the operation exactly once.
Skips polling entirely.
Forwards the token via the
X-Qonto-Sca-Session-Tokenheader.
This is the path used by step (2) of the two-step fallback. It is also useful when the LLM client implements its own polling cadence and only needs the wrapper to retry with an already-captured approval.
Sandbox testing
Sandbox accounts cannot enroll a real paired device, so SCA challenges in sandbox use a mock flow. After receiving a pending response, simulate the user's decision with the sca_session_mock_decision tool (sandbox-only — refuses to run when no staging token is configured). See docs/sandbox-testing.md for the full sandbox setup.
Migration note
Earlier QontoCtl builds (pre-@qontoctl/mcp SCA continuation) returned a free-form text response on 428 with no continuation hooks. Callers parsing that response should adopt the structured flow:
Before | After |
Free-form text mentioned the SCA endpoint but offered no MCP-exposed way to continue. | The SCA-pending response is still text content but its shape is stable: |
Polling required driving the Qonto HTTP API directly. | Use the |
Re-running the operation orphaned the prior approval. | Retry the original tool with the captured |
No way to opt-in to inline polling — every 428 was a dead end. | Pass |
The pending response's textual format is stable, so callers that need to extract the token programmatically can match against the Session token: line — but using sca_session_show directly avoids relying on the response prose.
CLI Usage
First command to try when something doesn't work:
qontoctl diagnose— a read-only healthcheck across config, credentials, scopes, organization metadata, and host routing.
Commands
Command | Description |
| Read-only healthcheck (see troubleshooting) |
| Show organization details |
| List bank accounts |
| Show bank account details |
| Download IBAN certificate PDF |
| Create a new bank account |
| Update a bank account |
| Close a bank account |
| List transactions with filters |
| Show transaction details |
| List attachments for a transaction |
| Attach a file to a transaction |
| Remove attachment(s) from a transaction |
| List bank statements |
| Show statement details |
| Download statement PDF |
| List all labels |
| Show label details |
| List organization memberships |
| Show current user's membership |
| Invite a new member |
| List SEPA beneficiaries |
| Show beneficiary details |
| Create a new beneficiary |
| Update a beneficiary |
| Trust one or more beneficiaries |
| Untrust one or more beneficiaries |
| List SEPA transfers |
| Show SEPA transfer details |
| Create a SEPA transfer |
| Cancel a pending SEPA transfer |
| Download SEPA transfer proof PDF |
| Verify a payee (VoP) |
| Bulk verify payees from CSV |
| Create an internal transfer |
| List bulk transfers |
| Show bulk transfer details |
| Create a bulk SEPA transfer from JSON |
| List recurring transfers |
| Show recurring transfer details |
| List Qonto Terminals (POS) |
| Initiate a payment on a terminal |
| List catalogue products |
| List clients |
| Show client details |
| Create a new client |
| Update a client |
| Delete a client |
| List client invoices |
| Show client invoice details |
| Create a draft client invoice |
| Update a draft client invoice |
| Delete a draft client invoice |
| Finalize client invoice and assign number |
| Send client invoice to client via email |
| Mark client invoice as paid |
| Unmark client invoice paid status |
| Cancel a finalized client invoice |
| Upload a file to a client invoice |
| Show upload details for a client invoice |
| List quotes |
| Show quote details |
| Create a new quote |
| Update a quote |
| Delete a quote |
| Send quote to client via email |
| List credit notes |
| Show credit note details |
| List supplier invoices |
| Show supplier invoice details |
| Create supplier invoices from files |
| Show e-invoicing settings |
| List all requests |
| Upload an attachment file |
| Show attachment details |
| Configure OAuth client credentials |
| Start OAuth login flow |
| Display OAuth token status (focused; for whole-integration health, use |
| Refresh the OAuth access token |
| Revoke OAuth consent and clear tokens |
| Create a named profile |
| List all profiles |
| Show profile details (secrets redacted) |
| Remove a named profile |
| Test credentials |
| Generate bash completions |
| Generate zsh completions |
| Generate fish completions |
| Start MCP server on stdio |
Global Options
Option | Description |
| Explicit path to a config file (overrides |
| Configuration profile to use |
| Output format: |
| Fetch a specific page of results |
| Results per page |
| Disable auto-pagination |
| Enable verbose output |
| Enable debug output (implies |
Configuration
QontoCtl supports two authentication methods:
API Key — production-only access using your organization slug and secret key. Supports the endpoints listed as "API key ✔" in the Qonto auth table (most reads plus many writes — internal transfers, clients, attachments, …). Cannot be used against the Qonto sandbox.
OAuth 2.0 — full access including OAuth-only endpoints (cards, teams, webhooks, e-invoicing, payment links, insurance, international transfers, recurring transfers, SCA flows) and the Qonto sandbox via staging-token; see the OAuth App Setup Guide.
Profile Format
All configuration files use the same YAML format:
# API Key authentication
api-key:
organization-slug: acme-corp-4821
secret-key: your-secret-key
# OAuth 2.0 authentication (see docs/oauth-setup.md)
oauth:
client-id: your-client-id
client-secret: your-client-secretResolution Order
The CLI resolves the config file in this order (highest priority first):
--config <path>flagQONTOCTL_CONFIG_FILEenv var~/.qontoctl/{name}.yaml(when--profile <name>is given)~/.qontoctl.yaml(home default)
When --config is supplied alongside QONTOCTL_CONFIG_FILE or --profile and the resolved paths disagree, --config wins and a warning is emitted on stderr so the override is visible.
No current-directory discovery. The CLI does not scan the working directory for
.qontoctl.yaml. For repo-local config, use adirenvshim that exportsQONTOCTL_CONFIG_FILE="$PWD/.qontoctl.yaml", or pass--config ./.qontoctl.yamlexplicitly per invocation.
Per-field overrides apply on top of the loaded file:
Without
--profile:QONTOCTL_*env vars override file valuesWith
--profile acme:QONTOCTL_ACME_*env vars override file values
For the full reference (precedence rules per entry point, profile semantics, migration from CWD discovery), see docs/configuration.md.
Environment Variables
Environment variables override file values. They carry inputs (static configuration) the tool reads but never writes back; runtime-mutable state (refresh tokens, token expiry, granted scopes) lives in the file only. See the note on QONTOCTL_ACCESS_TOKEN below.
Without --profile:
Variable | Description |
| Organization slug |
| API secret key |
| OAuth client ID |
| OAuth client secret |
| OAuth access token (read-only — see below) |
| Custom API endpoint |
| Staging token (activates sandbox URLs) |
With --profile <name>, prefix becomes QONTOCTL_{NAME}_ (uppercased, hyphens replaced with underscores). For example, --profile acme reads QONTOCTL_ACME_ORGANIZATION_SLUG.
QONTOCTL_ACCESS_TOKENsemantics: when set, the env-supplied bearer is used for the current invocation only. Proactive token refresh is not attempted, and refreshed tokens are not persisted to disk (mirrorsAWS_SESSION_TOKEN). If the token has expired the API surfaces a401; re-issue the token externally.
QONTOCTL_REFRESH_TOKENis intentionally not supported. Refresh tokens are runtime-mutable state — every refresh produces a new value the tool must write back somewhere — and env vars carry inputs, not state. Use file-based credentials (~/.qontoctl.yamlor a profile) for OAuth flows that need refresh, or stick with API-key env vars in CI.
Debug Mode
The --verbose and --debug flags enable wire-level logging to stderr:
qontoctl --verbose transaction list # request/response summaries
qontoctl --debug transaction list # full headers and response bodiesSecurity note:
--debuglogs full API response bodies. Known sensitive fields (IBAN, BIC, balance) are automatically redacted, but responses may still contain other financial data. Do not use--debugin shared environments or pipe debug output to files accessible by others.
Disclaimer
qontoctl is an independent project not affiliated with, endorsed by, or officially connected to Qonto. It runs on your own machine with your own credentials.
"Qonto" and the Qonto logo are trademarks of Olinda SAS (the company operating Qonto); qontoctl uses the name only to describe the service it interoperates with.
License
What AGPL means for you
Using qontoctl as a CLI tool or MCP server does not make your code AGPL-licensed. Running the tool, scripting around it, or connecting it to your applications is normal use — no license obligations arise.
Using
@qontoctl/coreas a library (importing it into your code) means your combined work is covered by AGPL-3.0. If you distribute that combined work, you must make its source available under AGPL-compatible terms.Modifying and distributing qontoctl itself requires you to share your changes under AGPL-3.0.
Commercial licensing is available if AGPL does not fit your use case — contact the maintainer.
Available Tools
73 toolsaccount_closeA
Close a bank account. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), wait, sca_session_token.
account_iban_certificateA
Download IBAN certificate PDF for a bank account
Inputs: id (required).
account_listA
List all bank accounts for the organization
Inputs: no named parameters.
account_showB
Show details of a specific bank account
Inputs: id (required).
beneficiary_addA
Create a new SEPA beneficiary. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: iban (required), name (required), bic, wait, +3 more.
beneficiary_listC
List SEPA beneficiaries in the organization
Inputs: iban, page, status, sort_by, +4 more.
beneficiary_trustA
Trust one or more SEPA beneficiaries (requires Embed-partner-only beneficiary.trust OAuth scope; standard third-party apps will receive 403). SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: ids (required), wait, sca_session_token.
beneficiary_untrustA
Untrust one or more SEPA beneficiaries (requires Embed-partner-only beneficiary.trust OAuth scope; standard third-party apps will receive 403). SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: ids (required), wait, sca_session_token.
beneficiary_updateA
Update an existing SEPA beneficiary. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), bic, iban, name, +4 more.
bulk_transfer_showA
Show details of a specific bulk transfer
Inputs: id (required).
card_appearancesB
List available card appearances (designs by type and level)
Inputs: no named parameters.
card_bulk_createA
Bulk create cards (up to 50). SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: cards (required), wait, sca_session_token.
card_discardA
Discard a card (irreversible). SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), wait, sca_session_token.
card_listC
List cards in the organization
Inputs: page, query, sort_by, per_page, +4 more.
card_report_lostA
Report a physical card as lost (irreversible). SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), wait, sca_session_token.
card_update_limitsA
Update a card's spending limits. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), wait, atm_daily_limit, atm_monthly_limit, +8 more.
card_update_nicknameA
Update a card's nickname. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), nickname (required), wait, sca_session_token.
card_update_restrictionsA
Update a card's restrictions (active days, merchant categories). SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), wait, categories, active_days, +1 more.
client_invoice_finalizeA
Finalize a client invoice (assign number, transition from draft to unpaid)
Inputs: id (required).
client_invoice_mark_paidB
Mark a client invoice as paid
Inputs: id (required).
client_invoice_sendB
Send a finalized client invoice to the client via email. Requires send_to (one or more recipient emails) and email_title; optional email_body and copy_to_self (default true).
Inputs: id (required), send_to (required), email_title (required), email_body, +1 more.
client_invoice_showB
Show details of a specific client invoice
Inputs: id (required).
client_invoice_unmark_paidA
Unmark a client invoice paid status (transition back to unpaid)
Inputs: id (required).
client_invoice_upload_showB
Show upload details for a client invoice
Inputs: id (required), upload_id (required).
client_listB
List clients with optional pagination
Inputs: page, per_page.
client_showB
Show details of a specific client
Inputs: id (required).
client_updateC
Update an existing client
Inputs: id (required), city, name, email, +9 more.
credit_note_showB
Show details of a specific credit note
Inputs: id (required).
diagnoseA
Run a read-only healthcheck against the configured qontoctl profile. Returns a DiagnosticReport with per-check status (ok/warn/fail/skip), detail, and suggested actions. Use this first when something doesn't work.
Inputs: profile.
einvoicing_settingsB
Retrieve e-invoicing settings for the organization
Inputs: no named parameters.
insurance_createC
Create a new insurance contract
Inputs: name (required), type (required), origin (required), status (required), +10 more.
insurance_remove_documentB
Remove a document from an insurance contract
Inputs: contract_id (required), document_id (required).
insurance_updateC
Update an insurance contract
Inputs: id (required), name, type, origin, +11 more.
intl_quote_createB
Create an international transfer quote with exchange rate
Inputs: amount (required), currency (required), direction.
intl_transfer_createA
Create an international transfer. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: quote_id (required), beneficiary_id (required), wait, fields, +1 more.
label_listC
List all labels in the organization
Inputs: page, per_page.
membership_inviteB
Invite a new member to the organization
Inputs: role (required), email (required), team_id, last_name, +1 more.
membership_listB
List all memberships in the organization
Inputs: page, per_page.
membership_showA
Show the current authenticated user's membership
Inputs: no named parameters.
org_showA
Show organization details including name, slug, and bank accounts
Inputs: no named parameters.
payment_link_connectC
Establish payment link connection with provider
Inputs: user_website_url (required), user_phone_number (required), partner_callback_url (required), user_bank_account_id (required), +1 more.
payment_link_connection_statusB
Get payment link connection status
Inputs: no named parameters.
payment_link_createB
Create a new payment link (basket or invoice type)
Inputs: payment_link (required).
payment_link_deactivateC
Deactivate a payment link
Inputs: id (required).
payment_link_listC
List payment links
Inputs: page, status, sort_by, per_page.
payment_link_methodsA
List available payment methods for payment links
Inputs: no named parameters.
payment_link_paymentsC
List payments for a specific payment link
Inputs: id (required), page, per_page.
payment_link_showA
Show details of a specific payment link
Inputs: id (required).
quote_deleteB
Delete a quote
Inputs: id (required).
quote_sendB
Send a quote to the client via email. Requires send_to (one or more recipient emails) and email_title; copy_to_self BCCs the authenticated user (defaults to true server-side).
Inputs: id (required), send_to (required), email_title (required), email_body, +1 more.
quote_showB
Show details of a specific quote
Inputs: id (required).
recurring_transfer_cancelA
Cancel a recurring transfer. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), wait, sca_session_token.
recurring_transfer_showA
Show details of a specific recurring transfer
Inputs: id (required).
request_approveA
Approve a pending request. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: id (required), request_type (required), wait, debit_iban, +1 more.
request_create_flash_cardA
Create a flash card request. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: note, wait, pre_expires_at, sca_session_token, +1 more.
request_create_virtual_cardA
Create a virtual card request. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: note, wait, card_level, card_design, +2 more.
sca_session_showA
Show the status of a Strong Customer Authentication (SCA) session. Use this to poll an SCA session token returned by a previous tool call that triggered an SCA challenge. Returns one of: waiting (the user has not yet responded), allow (approved — retry the original request), or deny (rejected). Tokens expire after 15 minutes.
Inputs: token (required).
statement_showB
Show details of a specific bank statement
Inputs: id (required).
supplier_invoice_bulk_createB
Create supplier invoices by uploading files from the filesystem
Inputs: file_paths (required).
supplier_invoice_showC
Show details of a specific supplier invoice
Inputs: id (required).
team_createB
Create a new team in the organization
Inputs: name (required).
team_listA
List all teams in the organization
Inputs: page, per_page.
terminal_payment_createA
Initiate a payment on a Qonto Terminal (POS). Returns 202 Accepted — the terminal must still physically accept the card before the payment settles. An offline terminal may hold the request open for up to ~120 seconds.
Inputs: amount (required), terminal_id (required), currency, metadata.
transaction_attachment_addB
Attach a file to a transaction from the filesystem
Inputs: file_path (required), transaction_id (required).
transaction_attachment_listA
List attachments for a transaction
Inputs: transaction_id (required).
transaction_listB
List transactions for a bank account with optional filters
Inputs: iban, page, side, status, +12 more.
transaction_showA
Show details of a specific transaction
Inputs: id (required).
transfer_bulk_verify_payeeC
Bulk verify payees (Verification of Payee / VoP)
Inputs: entries (required).
transfer_createA
Create a SEPA transfer. Provide either beneficiary_id (existing beneficiary) or beneficiary (inline beneficiary object with name and iban), but not both. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.
Inputs: amount (required), reference (required), bank_account_id (required), note, +7 more.
transfer_listB
List SEPA transfers with optional filters
Inputs: page, status, sort_by, per_page, +5 more.
transfer_proofA
Download SEPA transfer proof PDF (returns base64-encoded content)
Inputs: id (required).
transfer_showB
Show details of a specific SEPA transfer
Inputs: id (required).
webhook_updateC
Update an existing webhook subscription
Inputs: id (required), types, secret, description, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 73 tools
Every tool has a clearly distinct purpose, with unique resource-action pairs. Even similar operations like beneficiary_trust and beneficiary_untrust are opposites, preventing confusion.
The dominant pattern is 'resource_verb' (e.g., account_list, card_discard). Some tools like request_create_flash_card and transfer_bulk_verify_payee use compound verbs, but the overall convention is maintained.
73 tools is high but appropriate for the breadth of financial operations covered. However, the count may overwhelm agents, placing it at the upper boundary of reasonable scope.
The tool surface covers many domains (accounts, cards, transfers, invoices, etc.) but lacks key create operations (e.g., client invoice creation, individual supplier invoice creation) and some updates, leading to notable gaps.
Maintenance
Related MCP Connectors
MCP server for Product Management
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
MCP server for customer-io
Related MCP Servers
- -
- MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Holded — invoicing, accounting, CRM, projects, and team77 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for Maasy AI Marketing Copilot2179 npmMIT