emMCP — MCP Server for Dolibarr

emMCP — Connect your AI assistant to your Dolibarr

You already use an AI assistant every day. emMCP gives it access to your Dolibarr: your customers, invoices, products, orders, projects and documents. You ask your questions and give your instructions in the assistant you already know, and it works directly inside your ERP.

No new assistant to learn, no extra interface: you keep the tool you already use.

⚡ Three steps and you are running

1. Install and enable the module, like any other Dolibarr module.
2. Set the permissions of the user the assistant will act as. That is the whole configuration: the assistant inherits exactly those rights.
3. Add the connector in your AI client by pasting the URL the module shows you.

The setup page hands you the URL, the command and the configuration file ready to copy, depending on the client you use. It takes minutes.

🔌 Works with the clients you already use

• claude.ai (web and desktop) — custom connector with OAuth authentication: you sign in with your Dolibarr account and give your consent. No key to copy and paste.
• Claude Code — a single command to run.
• Anthropic API and any MCP client that speaks HTTP transport.

💬 What your assistant can do

Around twenty tools cover everyday Dolibarr work:

• Look things up — "Which invoices from this customer are unpaid?", "Find last week's order for Dupont"
• Create and edit — third parties, quotes, invoices, orders, products, projects, with their lines
• Chain business actions — validate a quote, turn it into an order, generate the PDF
• Handle documents — list, upload, download, generate PDFs from your Dolibarr templates
• Work with your custom fields, linked contacts and time tracking

The tools go through Dolibarr's REST API: what your assistant can see and do matches exactly what the linked user can see and do in the interface.

🔒 Your Dolibarr permissions are the rule

This is the module's founding principle. The assistant holds no rights of its own: it acts on behalf of a Dolibarr user, with that user's permissions, module by module. Want a read-only assistant for accounting? Create a read-only user. Want it to raise invoices but never touch payroll? That is a permission setting — the one you already know how to manage.

Authentication uses OAuth 2.1 (with PKCE and token rotation) or an API key depending on the client, and you can revoke access at any time.

📊 Read-only SQL queries — optional, off by default

For the analysis the REST API does not cover — multi-year aggregates, cross-table reporting, bespoke dashboards — the module can open read-only SQL access. It ships switched off and sits behind several independent locks:

• a global switch, off on installation;
• a Dolibarr permission, granted to nobody by default;
• a named opt-in, user by user;
• a specific guard for multi-company environments.

While any one of those is missing, the SQL tools do not even appear in the client's tool list.

Every query goes through a lexer and a SQL parser before reaching the server: only read statements pass. Writes, schema commands, multiple statements and password or key columns are refused — including when a write keyword is hidden inside a string literal. Joins, subqueries, UNION and aggregates work normally. Row count, duration and response size are capped, and every query is recorded.

📋 Knowing what the assistant looked at

Dolibarr permissions say what a user may read; they say nothing about how much. Someone entitled to look up customers one at a time is not thereby entitled to pull the whole customer base in an afternoon. The module fills that gap, in a tab of its own.

• Call log — one row per call: who, which tool, with which arguments, how long it took and how it ended. Tool results are never stored; arguments are, since they are what makes a call auditable, and they can be switched off if your policy requires it.
• Per-user rate limit — a cap on tool calls over a rolling window. A refusal answers the assistant with numbers it can act on rather than an opaque error. Only tool calls count: connecting and listing the tools consume nothing.
• Email alert — warns an administrator when one user's volume stands out, with a cooldown so an intensive session sends one message rather than fifty.
• Automatic purge — configurable retention, 90 days by default.

🛠️ Nothing to host, nothing to watch

emMCP runs inside your existing Dolibarr, like any PHP page. No service to start, no port to open, no container to maintain. If your Dolibarr answers, your MCP server answers.

⚙️ Requirements

• Dolibarr 16 or later, PHP 8.1 or later
• Dolibarr's REST API module enabled
• HTTPS access to your instance from the AI client
• An account with the AI provider of your choice — the module adds no subscription of its own

📚 Learn more

Full overview, connection guide and use cases: www.e-dem.com/en/produits/emmcp

🤝 Support

Support and updates provided by E-dem. A question before buying? Write to us, we answer.