Provides access to Qonto organization data and actions via MCP, including organization info, accounts, and transactions.
Configuration
View docs{
"mcpServers": {
"qonto-qonto-mcp-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"QONTO_API_KEY=<QONTO_API_KEY>",
"-e",
"QONTO_ORGANIZATION_ID=<QONTO_ORGANIZATION_ID>",
"-e",
"QONTO_THIRDPARTY_HOST=https://thirdparty.qonto.com",
"qonto/qonto-mcp-server:latest"
],
"env": {
"QONTO_API_KEY": "<QONTO_API_KEY>",
"QONTO_ORGANIZATION_ID": "<QONTO_ORGANIZATION_ID>",
"QONTO_THIRDPARTY_HOST": "https://thirdparty.qonto.com"
}
}
}
}You can extend Claude Desktop with the Qonto MCP Server to access your Qonto organization data and perform operations like viewing organization info, managing accounts, and reviewing transactions. This MCP brings your data and actions into your workflow with secure, contextual access through the MCP client.
Connect your Claude Desktop client to the Qonto MCP Server to start querying organization data, accounts, and transactions. You configure the MCP server so Claude can communicate with the Qonto API and your third‑party host. Use the available transport options to suit your environment, and keep your API key and organization ID secure. Once connected, you can request information like organization details, account balances, and transaction history, and you can perform read operations on your financial data through the MCP client.
Prerequisites: you need Claude Desktop installed on your machine. You also need access to your Qonto API key and your organization ID from your Qonto account settings.
Option 1: Docker Installation (Recommended) install the MCP server container and configure Claude Desktop to connect to it.
1) Pull the Docker image.
docker pull qonto/qonto-mcp-server:latest
2) In your Claude Desktop configuration file, add the Qonto MCP Docker server with the following settings.
{
"mcpServers": {
"Qonto MCP Docker": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e", "QONTO_API_KEY=<QONTO_API_KEY>", // <- change this with the API key from the settings page
"-e", "QONTO_ORGANIZATION_ID=<QONTO_ORGANIZATION_ID>", // <- change this with the organization id from the settings page
"-e", "QONTO_THIRDPARTY_HOST=https://thirdparty.qonto.com",
"qonto/qonto-mcp-server:latest"
]
}
}
}
```
"""The following is a full Docker configuration example you can paste into your config.
{
"mcpServers": {
"Qonto MCP Docker": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e", "QONTO_API_KEY=abcdefghihlmnopqrstuvxz123456",
"-e", "QONTO_ORGANIZATION_ID=qonto-organization-slug-1234",
"-e", "QONTO_THIRDPARTY_HOST=https://thirdparty.qonto.com",
"qonto/qonto-mcp-server:latest"
]
}
}
}
```
"""Option 2: Local Installation (more flexible if you want to run MCP locally without Docker). This requires the UV runtime.
1) Clone the MCP server repository to your local machine.
2) Install uv on your system.
On macOS you can install uv with Homebrew: brew install uv.
3) In your Claude Desktop configuration, add the Qonto MCP server using the local run command.
Note: You can optionally pass --transport streamable-http to use HTTP transport instead of the default stdio transport.
{
"mcpServers": {
"Qonto MCP": {
"command": "uv",
"args": [
"run",
"--with",
"mcp[cli]",
"--with",
"requests",
"mcp",
"run",
"<PATH_TO_CLONED_REPO_FOLDER, ie. ~/development/qonto-mcp/qonto_mcp/server.py>",
"--transport",
"stdio" // <- optional: change to "streamable-http" for HTTP transport
],
"env": {
"QONTO_API_KEY": "<QONTO_API_KEY>", // <- change this with the API key from the settings page
"QONTO_ORGANIZATION_ID": "<QONTO_ORGANIZATION_ID>", // <- change this with the organization id from the settings page
"QONTO_THIRDPARTY_HOST": "https://thirdparty.qonto.com",
"PYTHONPATH": "<PATH_TO_CLONED_REPO, ie. ~/development/qonto-mcp>" // <- change this
}
}
}
}
```
"""The full local configuration example runs the MCP server from your cloned repository path using UV and the mcp CLI, with stdio transport by default.
Configuration and security are important when working with MCP servers. Use the following environment variables to configure access and integration with Qonto.
- QONTO_API_KEY: Your Qonto API key (required)
- QONTO_ORGANIZATION_ID: Your organization ID (required)
- QONTO_THIRDPARTY_HOST: API host URL (defaults to https://thirdparty.qonto.com)
Transport options include stdio for most cases and streamable-http if you prefer HTTP-based communication.
If you run into issues, verify credentials, check the network connection to the API host, and restart Claude Desktop after configuration changes.
Troubleshooting tips address common problems like invalid credentials, timeouts, and missing server recognition by Claude Desktop.
Contributions and improvements are welcome. Ensure you follow best practices for securing API keys and organization IDs.
License terms apply as specified for this MCP server.
This MCP server provides programmatic access to your Qonto organization data through a configurable client. You can retrieve organization info, account details, and transaction history using the MCP interface.
Get details about your Qonto organization.
Access account information and balances.
Retrieve and analyze transaction data.
Access business-related financial data.