The Odoo MCP server that answers to policy.
Odient exposes your Odoo to any MCP client (Claude Desktop, Cursor, your own agents) as one endpoint with 131 tools across 15 modules. Every call passes the same five-layer firewall and write-gate as every other way into Odient, and every decision writes one audit record. MCP access is not a side door; it is the same governed front door.
tools/list → 131 tools · 15 modules
tools/call "account.invoice.overdue"
firewall → 5 layers · passed
policy → read · allowed
result → $279,496.75 · 2 customers · 31–60d
audit → one record · tied to you
Your Odoo, as tools a model can call.
The Model Context Protocol is how AI tools ask other systems for data and actions. Point your MCP client at Odient’s endpoint and your Odoo shows up as tools the model can call: read the pipeline, draft the reminder, trace the lot. The difference from wiring a model to the database directly: between the tool call and your records stands the whole governance layer.
→ one governed endpoint
→ identity · injection screen · tool scope · approval · audit
→ your Odoo · 17, 18 or 19
A call from Cursor is treated exactly like a question in Discuss.
Identity and access first, injection screening, tool-scope policy, per-action approval, and the audit row. Five gates, in order, every time. Scoped keys, short-lived session exchange, no long-lived all-powerful token. If the person behind the client is not cleared for a record, the client is not either. The refusal is logged too.
Getting started: install the Odient module on Odoo 17, 18 or 19, add the credential, and point your client at the endpoint. The docs walk the whole setup, first credential to first answer.
→ gate 2 injection screening
→ gate 3 tool-scope policy
→ gate 4 per-action approval
→ gate 5 audit & logging
→ your Odoo · auditable
Frequently asked questions.
What is an Odoo MCP server?
An MCP server for Odoo exposes your ERP’s data and actions as tools that AI clients such as Claude, Cursor and custom agents can call over the Model Context Protocol. Odient ships one as part of the platform: 131 tools across 15 Odoo modules, behind a five-layer firewall, with every call logged.
How is Odient different from an open-source Odoo MCP server?
Open-source servers connect a model to Odoo; the hard part is what they leave to you: access control, write approval, audit. In Odient, every MCP call runs as the requesting person’s own Odoo permissions, every write passes the gate you set, and every decision writes one audit record, allowed, blocked and approved alike.
Which clients work?
Anything that speaks MCP. Claude Desktop and Cursor are the ones teams use daily. The same endpoint serves Diana in Discuss and the Odient panel, so there is nothing extra to run.
Does it work on Odoo Community?
Yes: Community or Enterprise, versions 17, 18 and 19. Odoo 17 and 18 connect over XML-RPC, 19 over JSON-2 REST; the difference is handled for you.