Qonto-MCP-Server

MCP Server for the Qonto API enabling programmatic access to all endpoints via API key authentication.

other

3

GitHub Stars

other

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "j-about-qonto-mcp-server": {
      "command": "uvx",
      "args": [
        "qonto-mcp-server",
        "--api-key",
        "API_LOGIN:API_SECRET_KEY"
      ]
    }
  }
}

You can run the Qonto MCP Server to access all Qonto Business API endpoints via API key authentication. This server acts as a bridge, enabling you to connect your MCP client to Qonto programmatically and manage requests securely.

How to use

You run the MCP server locally and connect your MCP client to it. Use either the UVX runtime or Python to start the server, passing your API key pair to authorize requests. The server will proxy API calls to Qonto using your API key and expose them through your MCP client as defined endpoints.

How to install

Prerequisites you need before installing:

Python 3.x if you plan to run the server with Python using the -m approach.
UVX available if you prefer running directly with uvx.

Configuration and usage options

"mcpServers": {
  "qonto-mcp-server": {
    "command": "uvx",
    "args": ["qonto-mcp-server", "--api-key", "API_LOGIN:API_SECRET_KEY"]
  }
}

"mcpServers": {
  "qonto-mcp-server": {
    "command": "python",
    "args": ["-m", "qonto-mcp-server", "--api-key", "API_LOGIN:API_SECRET_KEY"]
  }
}

Notes on usage

Choose the method that fits your environment best. If you already have Python installed, the -m approach is straightforward. If you prefer a self-contained runtime, use UVX to run the server directly. Ensure your API key pair is kept secure and not exposed in client-side code.

Security considerations

Treat the API_LOGIN:API_SECRET_KEY pair as sensitive credentials. Use environment isolation where possible and rotate keys regularly. Limit the scope of the API key to only the endpoints you need.