Odoo MCP for Odoo 19.
Odoo 19.0 introduced JSON-2 as the external API. Odoo 19.4 lists MCP connectivity. New integrations should target JSON-2, not deprecated XML-RPC.
Odoo documents JSON-2 as new in 19.0. An MCP server needs a stable way to call models and methods; JSON-2 is that way for current Odoo.
What is JSON-2?
HTTP to /json/2/<model>/<method>, for example /json/2/res.partner/search_read, with bearer API-key authentication. Short-lived keys and one key per integration are the documented hygiene.
Why JSON-2 matters for MCP
Claude / ChatGPT / Gemini → MCP → JSON-2 → Odoo. Structured, HTTP-native, compatible with remote MCP servers that cannot install Python on the ERP host.
Deprecated RPCs
Building a new MCP server on XML-RPC in 2026 is choosing a dead end. Existing servers that still speak RPC need a JSON-2 path if they intend to stay on 19+.
Permissions and API keys
JSON-2 is not admin-by-default. Same access rights, record rules, field access. Dedicated keys per service.
Official API vs official MCP
JSON-2 is official in 19.0. MCP connectivity is listed in the Odoo 19.4 release notes. They are different layers. Community and vendor servers still exist beside both. Longer take: Is Odoo MCP official?. Related: Odoo Online, MCP + JSON-2 stack, external API cost.
Odoo 19 is not one thing
19.0 is JSON-2 and RPC deprecation. 19.4 is also MCP in the release notes. An article that says “Odoo 19 has MCP” without the minor version is how people open 19.1 and wonder where the menu is.
Community vs Enterprise vs Odoo Online vs odoo.sh vs your host are still different products that happen to share a version number. Confirm the combination you run before you tell the business “we’ll just enable MCP.”
New sidecar work on 19.x should still use JSON-2, not XML-RPC, even if you also use 19.4 MCP later. JSON-2 explained.
Not a replacement for access rights
Attaching Claude to Odoo 19 does not bypass record rules. If a salesperson cannot see other companies’ invoices, the bot user should not either — unless you built the bot as an admin, which is the bug.
It is not a replacement for Studio, webhooks, or scheduled actions. Those are software-to-software paths. MCP is for MCP-compatible agents asking questions and taking bounded actions.
It is not Odoo S.A. endorsing every GitHub repo titled odoo-mcp. Read the transport. Prefer JSON-2 or in-process ORM. Free Odoo MCP servers.
Official documentation
FAQ
What is JSON-2?
Odoo 19's HTTP API: endpoints like /json/2/res.partner/search_read, authenticated with a bearer API key. New in 19.0. Odoo 19 External API.
What about XML-RPC and JSON-RPC?
Odoo 19 deprecates the older external RPC APIs and points new work at JSON-2. They are scheduled for removal in Odoo 22 (fall 2028). External API.
Does JSON-2 mean unrestricted AI access?
No. Operations are checked against access rights, record rules and field access for the authenticated user.
Does Odoo 19 make MCP official?
JSON-2 is official in 19.0. Odoo 19.4 lists MCP connectivity in the release notes. A third-party server using JSON-2 is still that vendor’s software. Odoo 19.4 MCP · Is Odoo MCP official?.
The rest of the MCP cluster
Start read-only. Ask a real question.
Sandbox on sample data, or we put MCP on your instance.