Dolibarr

Turn the module on first. Dolibarr ships the REST API as a module that is off by default.

1. As an administrator go to Setup → Modules → Web Services API REST and enable it.
2. Open the user you want the agent to act as, go to the User card → API key area, and generate a key. Put it in DOLIBARR_API_KEY.
3. Set DOLIBARR_URL to your installation root (no trailing slash, no /api). The adapter appends /api/index.php.

The header is DOLAPIKEY. Not Authorization. Dolibarr also accepts it as a query parameter, but a header keeps it out of the access log.

Permissions follow the user, per module. Dolibarr's rights are fine-grained — a user with no read invoices permission gets a 403 on /invoices, and one with no read third parties sees an empty list. Grant exactly what the agent needs on a dedicated user.

sqlfilters is the powerful part. Dolibarr's list endpoints accept a filter expression like (t.datec:>=:'2026-01-01') and (t.fk_statut:=:1) — the colon-delimited operator syntax is Dolibarr's own and is documented on the wiki. Field names are the SQL column names, prefixed t..

Status codes are integers with per-object meanings. An invoice's status 0 is draft, 1 validated, 2 paid, 3 abandoned. An order's are different again. Do not assume they line up.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (erp.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.