MCP Server — AI-powered Dolibarr

MCP Server turns your Dolibarr into an AI-pilotable ERP. It exposes a standards-compliant Model Context Protocol (MCP) endpoint over JSON-RPC 2.0 / stateless HTTP, allowing Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), Mistral, and any MCP-compatible agent or orchestrator to read your data and execute business operations — without the module ever making a single outbound call to an AI vendor. The AI connects into your Dolibarr; your Dolibarr connects to nobody.

Why this module is different

Most "AI + ERP" integrations are chatbots that reformat data. MCP Server implements the real MCP protocol (revision 2025-06-18), the open standard from Anthropic now adopted industry-wide. This means:

• Native interoperability: any MCP client (Claude Desktop, claude.ai, OpenAI Agents, LangChain, AutoGen, CrewAI, n8n, Make…) connects without custom development.
• Structured tools with JSON Schema: the AI knows exactly which arguments to pass, eliminating hallucinations on parameters.
• MCP prompts and resources: beyond tools, the module exposes ready-made business prompt templates (lead qualification, proposal drafting, payment-reminder email) and addressable URI resources (dolibarr://thirdparty/{id}, dolibarr://invoice/{id}).

Security — The foundation

Security is not an afterthought: it is architectural.

Dedicated access tokens

Each AI client receives a unique token generated from 30 random bytes (mcp_xxxx…, 64 hex characters). Only the SHA-256 hash is stored in the database — exactly like GitHub PATs. The plaintext is shown once at creation; if you lose it, generate a new one. Each token carries:

• A specific Dolibarr user — the token acts on their behalf
• Scopes — allowed tool groups: thirdparty, sales, invoice, project, etc.
• An optional expiry date
• Last-used timestamp and last IP tracking

Two-layer authorization

An AI call is authorised only if:

1. The token is active, not expired, and the IP is on the allowlist (if configured)
2. The token scope includes the requested tool's group
3. The user bound to the token holds the native Dolibarr right for the operation (e.g. propal->creer to create a proposal, facture->paiement to record a payment)

Privilege escalation via a token is impossible. An admin with scope * is still limited to the acting user's rights.

Global configurable controls

Full audit trail

Every MCP call is recorded: timestamp, Dolibarr user, method, tool called, argument summary (secrets always redacted), ok/error status, duration in ms, client IP. Viewable directly in the module's administration interface.

27 business tools

🏢 Third parties & contacts (thirdparty)

📋 Sales (sales)

🧾 Invoices (invoice)

📁 Projects & agenda (project)

📦 Products (product)

📊 Analytics (analytics)

⚙️ System (system)

MCP prompts and resources

Ready-to-use prompts:

• qualify_lead — Guides the AI to qualify a prospect and suggest next steps in Dolibarr
• draft_proposal — Helps the AI structure a commercial proposal for a customer
• dunning_email — Generates a polite payment-reminder email for an overdue invoice

URI resources:

• dolibarr://thirdparty/{id} — Full third party record as JSON
• dolibarr://invoice/{id} — Full invoice record as JSON

Connecting an AI client

Claude Desktop / claude.ai: add a custom connector with the endpoint URL and the bearer token.

stdio-only clients (via mcp-remote):

{
  "mcpServers": {
    "dolibarr": {
      "command": "npx",
      "args": ["mcp-remote", "https://your-dolibarr/custom/mcpserver/mcp.php",
               "--header", "Authorization: Bearer YOUR_TOKEN"]
    }
  }
}

Requirements

• Dolibarr 22.0 or later
• PHP 8.1 or later