Videos · 1:06 · 2026-09-24

Odoo 20 native MCP vs the Execution Layer: what happens when your AI writes.

Odoo 20 native MCP vs the Execution Layer: what happens when your AI writes 1:06 · sound on
Real Execution Layer screens and real MCP responses on Odoo 19 with demo data; one key reference masked. The native side is shown as Odoo’s 20.0 documentation describes it.

One request, moving 12 customers to 21-day payment terms, through Odoo 20’s native MCP as its 20.0 docs describe it and through the Execution Layer on real screens: the change waits for a person, runs only as approved, is read back from the database, replays on retry instead of running twice, refuses an ambiguous name, and is recorded before and after.

Read the page: Odoo 20 native MCP vs the Execution Layer

Transcript

  1. Odoo 20 has MCP. What happens when your AI writes?
  2. The request: “Move these 12 customers to 21-day payment terms.”
  3. Odoo 20 native MCP, per Odoo’s 20.0 docs: the update runs. A person approving it first, a read-back from the database, and a record of what the AI did are not described.
  4. Execution Layer: The change waits for a person. (real response, demo data)
  5. A person approves, in Odoo: Approved payload only.
  6. Execution Layer: Read back from the database: Verified. (real response, demo data)
  7. The stored receipt: Executed · Persisted · Verified · Recorded
  8. A retried update: Retry runs once. (real response, demo data)
  9. Two companies named Northwind Trading: Refused, not guessed.
  10. Evidence · record history: Every change, before and after.
  11. Native MCP for reading. The Execution Layer for writes you can prove. nanti.ai/execution-layer. Available now for Odoo 19 · Odoo 20 support in progress · real product, demo data.

More videos

All videos