Buyer’s guide · Odoo 20 · updated 24 September 2026

What is the best MCP server for Odoo 20?

Not one name. The right level for the job your AI will do. Odoo 20 made connecting AI a built-in feature; enterprise-grade is what you need once that AI starts changing the records your business runs on.

The short answer

AI that reads and navigates: Odoo 20’s native MCP server is the natural choice. AI that writes: choose a server that reaches Level 3, where every change is approved when it matters, read back from the database, safe to retry, atomic, and recorded where no one can edit it. Score any candidate with the twelve checks below.

Written by nanti.ai. We wrote these criteria and we build one of the servers scored here, so judge the criteria as well as the scores.

Level 1 Connected The AI can reach Odoo, as a real user, starting read-only.
Level 2 Governed Who may do what is decided per person, on the server, with a human in the loop for risky changes.
Level 3 Proven Every write is checked against the database, safe to retry, atomic, and recorded where it cannot be edited.
Odoo 20 native MCP, per its docs Enterprise-grade

Native vs enterprise-grade

Three levels of MCP for Odoo.

Every MCP server for Odoo connects. The difference is how far up it goes. Each level includes the one below it.

Level 1

Connected

The AI can reach Odoo, as a real user, starting read-only.

Odoo 20’s native MCP server sits here, per its documentation.

  • Speaks MCP to the AI clients you use
  • Acts as a real user, inside that user’s Odoo rights
  • Starts read-only; writing is a deliberate choice
Level 2

Governed

Who may do what is decided per person, on the server, with a human in the loop for risky changes.

Where a business starts letting AI change records.

  • Each person signs in as themselves, with no key sitting in a config file
  • Per-person scopes decide which models, fields, and tools exist
  • Human approval, bound to the exact change
  • Business rules enforced on the server, not in the prompt
  • An off switch per person that works immediately
Level 3

Proven

Every write is checked against the database, safe to retry, atomic, and recorded where it cannot be edited.

What an AI writing to the books of record needs.

  • Success only after a database read-back
  • A retried request runs once
  • Multi-step changes are all or nothing
  • A tamper-resistant record of every call and refusal, with before and after values

Level 1 vs Level 3, on real screens

A one-minute walkthrough: the same AI request through Odoo 20’s native MCP, as its documentation describes it, and through the Execution Layer, where it is approved, verified, replayed safely, refused when ambiguous, and recorded.

Odoo 20 native MCP vs the Execution Layer 1:06 · sound on
Real Execution Layer screens and responses on Odoo 19, demo data. Native side per Odoo’s 20.0 docs.

Use case by use case

Which level does your AI’s job need?

Answer questions, build reports, summarise
Open views, filter lists, navigate Odoo
Update single records, with a person watching
Create quotations and leads for review
Bulk updates across many customers or products
Confirm orders, post invoices and bills
Message customers on WhatsApp or in Discuss
Unattended agents running on a schedule

The rule of thumb: the moment an AI can change money, stock, or what a customer receives, you want Level 3.

Score any server

The twelve-check scorecard.

Two columns are filled in: Odoo 20’s native server from its 20.0 documentation, and the Execution Layer from its product source. Tick the third for the server you are evaluating and watch its level.

Level 1 · Connected
01
Speaks MCP to the AI clients you use Ask: Which AI clients do you document, and how do they connect?
Odoo 20 native: Yes Claude Code, Claude Desktop, Codex, Antigravity, through mcp-remote Execution Layer: Yes
02
Acts as a real user, inside that user’s Odoo rights Ask: Whose access rights does a call run under, and can it ever exceed them?
Odoo 20 native: Yes Runs with the key owner’s access rights Execution Layer: Yes
03
Starts read-only; writing is a deliberate choice Ask: What can the AI change on day one, before anyone configures anything?
Odoo 20 native: Yes Five tools on by default, all read-only Execution Layer: Yes Write tools stay absent until an administrator turns writes on
Level 2 · Governed
04
Each person signs in as themselves, with no key sitting in a config file Ask: How does a person authenticate, where is the credential stored, and how long does it live?
Odoo 20 native: Partly A static API key per user, placed in the client’s config Execution Layer: Yes
05
Per-person scopes decide which models, fields, and tools exist Ask: Can two people using the same AI client see different tools and fields?
Odoo 20 native: Partly Tools are exposed per database, not per person Execution Layer: Yes
06
Human approval, bound to the exact change Ask: If a person approves an action, can the AI then run something different?
Odoo 20 native: Not described Not described in the 20.0 MCP docs Execution Layer: Yes
07
Business rules enforced on the server, not in the prompt Ask: Where do rules like “an order needs a customer reference” live, and what happens when they fail?
Odoo 20 native: Not described Not described in the 20.0 MCP docs Execution Layer: Yes
08
An off switch per person that works immediately Ask: How fast can an administrator stop one person’s AI access, and does it touch their Odoo rights?
Odoo 20 native: Partly Keys expire or can be deleted; no administrator switch described Execution Layer: Yes
Level 3 · Proven
09
Success only after a database read-back Ask: After a write, do you re-read the committed record, or return what the tool reported?
Odoo 20 native: Not described Not described in the 20.0 MCP docs Execution Layer: Yes
10
A retried request runs once Ask: If a request times out and the client retries, can the write happen twice?
Odoo 20 native: Not described Not described in the 20.0 MCP docs Execution Layer: Yes
11
Multi-step changes are all or nothing Ask: If step seven of ten fails, what happens to steps one to six?
Odoo 20 native: Not described Not described in the 20.0 MCP docs Execution Layer: Yes
12
A tamper-resistant record of every call and refusal, with before and after values Ask: Can an administrator edit or delete the log of what the AI did, and are refusals in it?
Odoo 20 native: Not described Not described in the 20.0 MCP docs Execution Layer: Yes
Result Level 1 4.5 of 12 checks · all of Level 1 Level 3 12 of 12 on Odoo 19 · Odoo 20 support in progress Level 0 0 of 12 ticked
See the full native comparison

Scoring: a level counts only when every check in it and below it is met. “Partly” counts half toward the total, never toward a level. Native marks read Odoo’s 20.0 MCP documentation on 24 September 2026; “not described” is not the same as “cannot”.

Your options on Odoo 20

Four kinds of MCP server.

Level 1 per its docs

Odoo 20’s native MCP server

Built into the AI app at your database URL plus /mcp. The natural first choice for reading and navigating on Odoo 20 with the AI app. Not in Odoo Community.

Set it up
Varies: score it

Open-source gateways

External servers that reach Odoo over its APIs, often free and well engineered. On Odoo 20 their data calls keep working; database management over RPC does not. Score each one yourself.

See the landscape
Varies: score it

Installed Apps Store modules

MCP servers that run inside your Odoo. Before relying on one for Odoo 20, ask for its test results on 20.0, not only the version it is listed for.

See the landscape
Level 3 on Odoo 19

The Execution Layer for Odoo

Our enterprise MCP server, built against the twelve checks on this page. It runs beside Odoo’s own /mcp, under /nanti/mcp. Available now for Odoo 19; Odoo 20 support in progress.

Compare with native

Plain answers

Choosing an Odoo MCP server, answered.

What is the best MCP server for Odoo 20?

The one that reaches the level your AI’s job needs. For reading, reporting, and navigating on Odoo 20 with the AI app, Odoo’s native MCP server is the natural choice. For an AI that confirms orders, posts invoices, updates many records, or messages customers, choose a server that proves what it did: approval bound to the exact change, a read-back from the database after every write, retry safety, all-or-nothing multi-step changes, and a tamper-resistant record of every call.

What makes an MCP server enterprise-grade for Odoo?

Three levels. Connected: it speaks MCP, acts as a real user within their Odoo rights, and starts read-only. Governed: each person signs in as themselves, scopes and approvals are set per person on the server, business rules are enforced, and access can be switched off at once. Proven: success is reported only after a database read-back, retries run once, multi-step changes are atomic, and every call and refusal is recorded where it cannot be edited.

Is Odoo 20’s native MCP server enterprise-grade?

It is a solid Level 1 server by its own documentation: built in, running as the user, and starting read-only. Odoo’s 20.0 MCP documentation, as of 24 September 2026, does not describe per-person scopes, approvals, business-rule enforcement, database read-back, retry safety, atomic multi-step changes, or an audit of AI calls, which the higher levels require. For an AI that only reads, that is often all you need.

Do I need an enterprise-grade MCP server if my AI only reads Odoo?

Usually not. Reading carries far less risk than writing, and a Level 1 server that runs as the user and starts read-only covers it. The exceptions are sensitive data, where you want per-person field scopes, and reports people rely on, where you want reads that say when they were cut short.

Which MCP server works with Odoo 20 Community?

Not Odoo’s native one: the Odoo 20 Community source code contains no MCP or AI module. Community users choose an external gateway that uses Odoo’s APIs or an MCP server installed as a module. The Execution Layer for Odoo supports Community and Enterprise; it is available now for Odoo 19, with Odoo 20 support in progress.

How do I compare MCP servers for Odoo?

Ask each vendor the twelve questions on this page and score the answers: which clients connect, whose rights a call runs under, what the AI can change on day one, how people authenticate, whether scopes are per person, whether approvals are bound to the exact change, where business rules live, how fast access can be switched off, whether writes are read back, whether retries can double-write, what happens when a multi-step change fails midway, and whether the log of AI actions can be edited.

Can I run Odoo’s native MCP server and an enterprise MCP server together?

Yes, if the enterprise server uses its own endpoint. The Execution Layer answers at /nanti/mcp and Odoo’s native server at /mcp, so both can run on one database: native for reading and navigating, the enterprise server for writes that need approval, proof, and evidence.

Does the Execution Layer work with Odoo 20?

Not yet; it is available today for Odoo 19, Community and Enterprise, self-hosted and Odoo.sh. Odoo 20 support is in progress: we have run our full failure suite against Odoo 20.0 Community and are porting the Odoo 20 API changes, for delivery as the first maintenance release, no later than eight weeks after Odoo 20’s general availability. The license is USD 499 one-time per Odoo major version, and existing customers move to the next major at half price. It runs beside Odoo’s own /mcp endpoint, under /nanti/mcp, so the two never collide.

Go deeper

Connected is the start. Proven is the bar.

The vendor landscape is in Odoo MCP servers, compared. The native server, head to head with ours, is in Odoo 20 native MCP vs the Execution Layer, and how Level 3 is built is in the technical whitepaper.

Evaluating an AI tool that writes to your Odoo?

Name it. We read its public docs and your description and tell you, in writing within five working days, whether it checks the proposal before it writes, logs the result, or re-reads the committed row after. Sourced line by line, using the same pre-registered method as our public write-verification census. Free, no pitch, and we tell you the truth even if the tool is not ours.

Get the Write-Check

Our own write-verification, the Execution Layer for Odoo, is available now. The verdict stays honest either way.

Not ready to talk? Follow what we ship.

An email when something real ships. No newsletters, no spam.

Living this problem every day and want to shape what comes next? We work closely with a small number of Odoo teams on the Execution Layer for Odoo, the ones who cannot fully trust what their AI writes to production today. Tell us about your Odoo setup.