Compatibility and versions.

Trust is earned in the boring places: what happens when Odoo changes, and whether you find out at the handshake or in production.

What is supported

• Odoo 19, Community and Enterprise. Both are covered and tested.
• Self-hosted or Odoo.sh. Not Odoo Online (no custom server modules there; those users have Odoo’s native MCP server).
• One Odoo database per host (dbfilter / monodb) is the supported deployment.

MCP protocol versions

The server speaks these MCP protocol revisions, preferring the newest:

2025-06-18   preferred
2025-03-26
2024-11-05

Drift detection

Every toolset carries a semantic toolset_version and a tool_schema_hash, and the server reports its version surface in every initialize. A client can pin to a hash, so a changed Odoo or a changed toolset is detected at the handshake, not discovered in production. There is an Odoo version adapter layer from day one, so support for a new Odoo major is an update, not a rewrite.

The compatibility contract

At launch, the Execution Layer publishes a compatibility contract: the Odoo versions it supports, in writing, with new Odoo major versions covered under an active Complete subscription. Odoo 20 is planned as the first maintenance delivery after launch; there is already an informational, allowed-to-fail Odoo 20 check in continuous integration.

For the machine-readable failures the server returns, see the error codes reference.