Qonto MCP Server

Qonto MCP Server

Enables interaction with the Qonto API v2 via 21 tools for organization, transactions, attachments, beneficiaries, clients, invoices, labels, memberships, requests, statements, and transfers, with GitHub OAuth authentication and stateful sessions.

Category
Visit Server

README

Qonto MCP Server

A remote Model Context Protocol server for the Qonto API, deployed on Cloudflare Workers with GitHub OAuth authentication.

Features

  • 21 tools covering the full Qonto API v2: organization, transactions, attachments, beneficiaries, clients, invoices, labels, memberships, requests, statements, and transfers
  • OAuth 2.1 authentication via GitHub (Authorization Code + PKCE)
  • Stateful sessions via Cloudflare Durable Objects
  • Zero cold-start secrets — Qonto credentials never leave Cloudflare

Tools

Category Tools
Organization get_qonto_organization
Transactions get_qonto_transactions, get_qonto_transaction, list_qonto_transaction_attachments
Attachments get_qonto_attachment
Beneficiaries list_qonto_beneficiaries, get_qonto_beneficiary
Clients get_clients, get_client
Invoices get_client_invoices, get_supplier_invoices, get_credit_notes
Labels list_qonto_labels, get_qonto_label
Memberships list_qonto_memberships
Requests get_requests, get_request
Statements get_statements, download_statement
Transfers list_qonto_external_transfers, get_qonto_external_transfer

Prerequisites

  • Node.js 18+
  • Wrangler CLI (npm install -g wrangler)
  • A Cloudflare account
  • A Qonto account with API access (Settings → Integrations → API)
  • A GitHub OAuth App

Setup

1. Clone and install

git clone git@github.com:thomas-rx/qonto-mcp-worker.git
cd qonto-mcp-worker
npm install

2. Create a GitHub OAuth App

Go to github.com/settings/developersOAuth AppsNew OAuth App.

Field Value
Homepage URL https://<worker-name>.<account>.workers.dev
Authorization callback URL https://<worker-name>.<account>.workers.dev/callback

For local development, create a second app with http://localhost:8788 and http://localhost:8788/callback.

3. Create the KV namespace

npx wrangler kv namespace create "OAUTH_KV"

Copy the returned ID into wrangler.jsonc:

"kv_namespaces": [{ "binding": "OAUTH_KV", "id": "<your-id>" }]

4. Set secrets

npx wrangler secret put QONTO_API_KEY
npx wrangler secret put QONTO_ORGANIZATION_ID
npx wrangler secret put GITHUB_CLIENT_ID
npx wrangler secret put GITHUB_CLIENT_SECRET
openssl rand -hex 32 | npx wrangler secret put COOKIE_ENCRYPTION_KEY

5. Local development

Copy .dev.vars.example to .dev.vars and fill in your credentials:

cp .dev.vars.example .dev.vars
npm run dev
# → http://localhost:8788

6. Deploy

npm run deploy

Connecting to Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "qonto": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<worker-name>.<account>.workers.dev/<mcp-path>"
      ]
    }
  }
}

On first connection, a browser window will open for GitHub authentication. Sessions persist for 30 days.

Architecture

Request → OAuthProvider
            ├── /authorize   → GitHub OAuth consent flow
            ├── /callback    → Token exchange + Qonto session
            ├── /token       → OAuth token endpoint
            ├── /register    → Dynamic client registration
            └── /<mcp-path>  → QontoMCP (Durable Object)
                                └── QontoClient → Qonto API v2

Environment Variables

Variable Required Description
QONTO_API_KEY Yes Qonto secret key
QONTO_ORGANIZATION_ID Yes Qonto organization slug
QONTO_THIRDPARTY_HOST No Override API base URL (default: https://thirdparty.qonto.com)
QONTO_STAGING_TOKEN No Qonto staging token
GITHUB_CLIENT_ID Yes GitHub OAuth App client ID
GITHUB_CLIENT_SECRET Yes GitHub OAuth App client secret
COOKIE_ENCRYPTION_KEY Yes 32-byte hex key for signing cookies

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured