mcp-server-dolibarr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOLIBARR_URL | Yes | Your Dolibarr REST API base URL | |
| DOLIBARR_API_KEY | Yes | The API key generated for your Dolibarr user |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dolibarr_pingA | Check that the configured Dolibarr URL and API key work, by fetching a single thirdparty record. |
| dolibarr_list_thirdpartiesA | List thirdparties (clients/suppliers) in Dolibarr. Supports basic filtering and pagination. |
| dolibarr_get_thirdpartyA | Get a single Dolibarr thirdparty (client/supplier) by its ID. |
| dolibarr_find_thirdparty_by_emailA | Find a Dolibarr thirdparty (client/supplier) by email address. |
| dolibarr_create_thirdpartyC | Create a new thirdparty (client/supplier) in Dolibarr. |
| dolibarr_update_thirdpartyB | Update fields on an existing Dolibarr thirdparty. |
| dolibarr_list_proposalsC | List commercial proposals (quotes) in Dolibarr. |
| dolibarr_get_proposalA | Get a single commercial proposal (quote), including its lines, by ID. |
| dolibarr_create_proposalA | Create a new commercial proposal (quote) header. Add line items afterwards with dolibarr_add_proposal_line. |
| dolibarr_add_proposal_lineC | Add a line item to an existing commercial proposal. |
| dolibarr_validate_proposalA | Validate (confirm) a draft commercial proposal so it can be sent to the client. |
| dolibarr_list_contractsC | List contracts in Dolibarr. |
| dolibarr_get_contractA | Get a single contract, including its lines, by ID. |
| dolibarr_create_contractB | Create a new contract header. Add line items afterwards with dolibarr_add_contract_line. |
| dolibarr_add_contract_lineB | Add a line item to an existing contract (e.g. an annual hosting/maintenance service). |
| dolibarr_list_invoicesC | List invoices in Dolibarr. |
| dolibarr_get_invoiceA | Get a single invoice, including its lines and payment status, by ID. |
| dolibarr_create_invoiceA | Create a new invoice header (draft). Add line items afterwards with dolibarr_add_invoice_line, then validate it. |
| dolibarr_add_invoice_lineC | Add a line item to an existing draft invoice. |
| dolibarr_validate_invoiceC | Validate a draft invoice, assigning it a definitive invoice number. |
| dolibarr_get_invoice_pdf_urlA | Build the Dolibarr web URL where a generated invoice PDF can be downloaded/printed in the browser (requires a logged-in Dolibarr session). |
| dolibarr_requestA | Make a raw authenticated request to any Dolibarr REST API endpoint not covered by the dedicated tools above (e.g. /products, /users, /projects, /agendaevents). Path is relative, e.g. '/products?limit=10'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool targets a distinct resource (contract, invoice, proposal, thirdparty) and action (create, add_line, get, list, validate, find, update). The catch-all 'dolibarr_request' tool is clearly distinguished as a generic fallback. There is no ambiguity or overlap.
All tools follow a consistent 'dolibarr_verb_noun' pattern (e.g., create_invoice, list_proposals). The only exception is 'dolibarr_request', which is a generic tool and intentionally deviates. Overall, naming is highly predictable and uniform.
22 tools cover multiple ERP entities (thirdparties, contracts, invoices, proposals) with appropriate CRUD-like operations. The number is well-scoped for a comprehensive integration without being excessive.
The tool set covers core workflows for thirdparties, contracts, invoices, and proposals, including creation, line addition, retrieval, listing, and validation. Missing are update and delete operations for most entities, but the raw request tool can compensate. Minor gaps in update/delete completeness.