{"id":"qonto-mcp-server","name":"qonto-mcp-server","homepage":"https://pypi.org/project/qonto-mcp-server/","repo_url":"https://github.com/j-about/Qonto-MCP-Server","category":"devtools","subcategories":[],"tags":["mcp","python","qonto","api","finance","agent-tools"],"what_it_does":"Provides an MCP server (CLI) that allows an agent to access Qonto’s Business API endpoints that are available via Qonto API key authentication.","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"],"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.","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)"],"af_score":39.2,"security_score":51.0,"reliability_score":25.0,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:46:56.881149+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["API key (combined as API_LOGIN:API_SECRET_KEY via --api-key)"],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided for the MCP server package itself; Qonto API usage costs (if any) are not addressed in the provided materials."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":39.2,"security_score":51.0,"reliability_score":25.0,"mcp_server_quality":55.0,"documentation_accuracy":45.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":70.0,"scope_granularity":20.0,"dependency_hygiene":70.0,"secret_handling":35.0,"security_notes":"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.”","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":40.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"unknown","retry_guidance_documented":false,"known_agent_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."]}}