qonto-mcp-server

Provides an MCP server (CLI) that allows an agent to access Qonto’s Business API endpoints that are available via Qonto API key authentication.

Evaluated Apr 04, 2026 (27d ago)

Homepage ↗ Repo ↗ DevTools mcp python qonto api finance agent-tools

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

The provided README indicates API key usage via a CLI argument. Whether the server uses HTTPS/TLS, how it stores/handles secrets in memory/logs, and whether it provides redaction are not specified. Scope granularity and endpoint-level authorization controls are not described beyond “accessible with API key authentication.”

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want to connect an LLM/MCP-capable desktop client to Qonto using an API key for a set of Business API endpoints.

Avoid When

You require strong documented guarantees around error handling, retries, pagination behavior, or fine-grained authorization scopes per operation.

Use Cases

• Agent-assisted querying of business data from Qonto (e.g., retrieving resources available via the Qonto Business API)
• Building internal automations where an LLM needs read/write actions against Qonto using an MCP-enabled client (e.g., Claude Desktop)
• Prototyping finance/accounting workflows via natural-language tool calls backed by Qonto’s API

Not For

• General-purpose Qonto API SDK usage outside of MCP clients
• Use cases requiring OAuth flows or user-scoped delegated permissions
• Environments needing documented pagination/retry/idempotency semantics for each Qonto endpoint

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: API key (combined as API_LOGIN:API_SECRET_KEY via --api-key)

OAuth: No Scopes: No

Authentication is described as Qonto API key auth passed to the MCP server CLI. The README does not discuss fine-grained scopes beyond what the Qonto API key provides.

Pricing

Free tier: No

Requires CC: No

No pricing information provided for the MCP server package itself; Qonto API usage costs (if any) are not addressed in the provided materials.

Agent Metadata

Pagination

unknown

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Authentication is passed as --api-key 'API_LOGIN:API_SECRET_KEY'; ensure secrets are not logged by your MCP host/client.
⚠ The README does not document rate limits, retries, pagination, or idempotency behavior for specific endpoints, so agents may need defensive handling.

Alternatives

Use Qonto’s official Business API directly from your application with an API key Use an HTTP client + Qonto OpenAPI/docs to implement only the needed endpoints Create/extend an MCP server in-house using the Qonto API directly (with your own security/retry/pagination handling)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for qonto-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.