Summary
The whole Odoo model layer, one connection wide.
Because the tools take a model name rather than wrapping specific business objects, anything in the instance is reachable — partners, invoices, stock, custom models alike. That generality cuts both ways: delete is in the set, and the Odoo account's permissions are the only boundary.
What it is
A TypeScript MCP server that connects to any Odoo instance over XML-RPC and exposes the standard Odoo record operations.
What you get
- Record search against any Odoo model with a domain filter and a limit
- Records read by ID with a chosen field list, and search combined with read in one call
- A count of matching records for when you want the number, not the rows
- Field definitions for a model, which is what makes querying an unfamiliar model possible
- Records created, written to, and deleted
- Per-project and per-environment configuration, chosen with `--project` and `--environment` on the launch command
Requirements
Odoo credentials: ODOO_URL, ODOO_DATABASE, ODOO_USERNAME and ODOO_PASSWORD, which take priority over the config file at ~/.odoo_config/. Node with npm for the install. The account's own Odoo permissions decide what the tools can reach.
Setup effort
One command plus a key — npm install -g ., then supply credentials