Qonto MCP Server

Qonto now runs the server itself at mcp.qonto.com, authenticating over OAuth and supporting both reads and writes against a business account. The GitHub repository still carries the earlier local build, which takes an organisation ID and API key from the account's integrations settings and runs either as a published Docker image or as a uv-launched Python process with an optional streamable-HTTP transport instead of stdio. That repository states plainly that it is no longer actively maintained and that the hosted server should be preferred, a distinction easy to miss when a directory links to the code rather than the product. Qonto also devotes a section of the README to MCP prompt-injection risk, which is a defensible amount of caution for a server sitting on a company's bank account.