In April, Connecting AI Agents to Odoo with MCP compared the four MCP servers for Odoo that existed then: mcp-server-odoo, muk_mcp, rag_odoo_mcp_server and Apexive’s LLM MCP. It picked muk_mcp as the place to start, and ended on a gap none of them had closed: there was no OAuth sign-in, so every user had to create an API key by hand and paste it into their AI app.
Seven months later, most of that gap is closed. Odoo S.A. ships its own MCP server with OAuth, the OCA has one, several of the original four moved on, and the Odoo app store lists several hundred MCP modules where there used to be a handful. This post goes through what changed, puts the options side by side and says what we would pick now.
Odoo’s own server, in short
Odoo’s ai_mcp comes with the AI app in Odoo 20 Enterprise (Odoo Online 19.4
had a first version with API keys only). It signs users in with OAuth, runs every call with the
signed-in person’s rights, and exposes five reading tools by default. I
tested it with Claude Code in Odoo’s Own MCP Server: Six Real Requests and What It Still Lacks. Reading was safe and
useful. What it lacks: there is no read-only choice per app or per token, Odoo
does not ask before writing, and there is no screen showing what the agent
did. It is also not available on Community or on 19.0 and older, which is
where the options below matter most.
OCA: ai_oca_mcp
The OCA’s AI repository3 has its own MCP server,
ai_oca_mcp, from Dixmit. Instead of general access to the data, each MCP
server record exposes a chosen list of tools. Each client gets its own API
key, shown once and with its own expiry, and calls go to an MCP Server Log
inside Odoo.
As of 6 November, it is merged only for 16.0
(#684, merged in May, beta). Migration pull requests
for 17.0, 18.0 and 19.0 are open, and so is an OAuth add-on,
ai_oca_mcp_oauth, for 16.0 (#1335).
Until that lands, Claude Desktop cannot connect, because it needs OAuth.
The module only exposes OCA ai_tool tools of the generic kind, so what the
agent can do depends on which tools you install. That is stricter than Odoo’s
approach and suits a database where you want to allow three specific actions
and nothing else. Unless you are on 16.0, I would follow it for now rather
than deploy it.
The original four, seven months on
mcp-server-odoo6 went from v0.5 to v0.9.0 (10 October). It added aggregation, posting chatter messages, field inspection and calling model methods (opt-in), plus the JSON-2 API for Odoo 19 and later. Its OAuth pull request was closed without merging, and its HTTP mode still has no authentication of its own. It is still what you use when one agent needs to reach several databases.
muk_mcp10 now covers Odoo 15.0 to 20.0, with 22 built-in tools (14 read, 8 write). It supports the newest MCP protocol revision, read-only or read-write keys, resources and prompts, and revocable sessions, and keeps its rate limit and 30-day audit log. OAuth is a separate paid add-on, muk_mcp_oauth11.
rag_odoo_mcp_server12 now recommends OAuth (“Sign in with Odoo”) and keeps per-user API keys as a fallback. It still covers 15.0 to 20.0, and is still paid.
LLM MCP by Apexive13 has a 19.0 version, but its repository has been quiet since May.
New modules worth knowing
Searching the Odoo app store for “mcp” on 6 November gave 308 modules for 19.0 and 167 for 20.0. I did not go through all of them; most repeat the same few ideas. The one I would look at first is mcp_server9 by much. Consulting.
It started as the companion module for mcp-server-odoo and was the most downloaded MCP module for 19.0 in the Odoo app store on 6 November. It has grown into a full MCP server inside Odoo, free and available for 16.0 to 20.0. Its listing promises:
- OAuth 2.1 with dynamic registration, PKCE and refresh tokens;
- a default-deny model list, with read, create, write and delete switches per model;
- a read-only consent scope, so a user can grant an agent read access only;
- an opt-in MCP User group, rate limits and an audit log of calls, denials and logins.
That covers most of what the official server lacks, on paper. I have not tested it yet, so treat this as what the listing says.
Side by side
Rows other than the official server come from each project’s documentation or listing on 6 November 2026, or from the first post where nothing changed. Only the official server was tested, in the hands-on post.
| Solution | Type | Odoo version | OAuth | Limit what the agent can write | Audit in Odoo | Price |
|---|---|---|---|---|---|---|
| ai_mcp (Odoo, tested) | Odoo module | 20 Enterprise (19.4 Online: keys only) | ✓ (no refresh) | Per tool, optionally per group | - | Included |
| ai_oca_mcp (OCA) | Odoo module | 16.0 (17.0 to 19.0 in review) | Add-on in review | Chosen tools per server | ✓ | Free |
| mcp_server (much.) | Odoo module | 16.0 to 20.0 | ✓ (listing) | Per model and operation, plus read-only scope (listing) | ✓ (listing) | Free |
| muk_mcp | Odoo module | 15.0 to 20.0 | Paid add-on | Read-only or read-write keys | ✓ | Free |
| mcp-server-odoo | External | 16.0+ | - | Through the Odoo user's rights | - | Free |
| rag_odoo_mcp_server | Odoo module | 15.0 to 20.0 | ✓ | Read-only or full tokens | - | Paid |
| LLM MCP (Apexive) | Odoo module | 16.0, 18.0, 19.0 | - | Through the Odoo user's rights | ✓ (April) | Free |
What we would pick now
flowchart TD
A{"Odoo 20<br/>Enterprise?"} -->|yes| B{"Need per-model limits,<br/>read-only grants or<br/>an audit screen?"}
A -->|no| E{"One agent across<br/>several databases?"}
B -->|no| C["Official ai_mcp"]
B -->|yes| D["much. mcp_server<br/>or muk_mcp<br/>(not tested here)"]
E -->|no| D
E -->|yes| F["mcp-server-odoo<br/>(no OAuth)"]On Odoo 20 Enterprise, start with the official server. It comes with the AI app, OAuth works without setup for the main AI apps, and it respects access rights. Leave the write tools off until you know which ones you need, limit them to a group with Allowed Groups, and connect agents through users with narrow rights instead of relying on the AI app to ask first. In our test, the agent created a quotation at a loss without a word.
If you need per-model limits, a read-only grant or an audit screen, look at
much. Consulting’s mcp_server (per model) or muk_mcp (per key). The same
two are the options on Community and on 16.0 to 19.0. I have not tested
either, so try them on a copy of your database first; keep an eye on the
OCA’s ai_oca_mcp if you prefer a curated tool list maintained by the OCA.
For one agent working across several databases, mcp-server-odoo is still the external option, without OAuth.
In April the missing piece was a safe way to sign in, and Odoo’s own server now has one. OAuth settles who the agent acts for. How much it may do with that person’s rights is a separate decision: a sales manager can delete quotations by hand, but you may not want an AI app acting for them to do it. That decision, per database and per group, is the part left to you.
-
MCP server (20.0 documentation) — Odoo
-
Authorization (2025-11-25 specification) — Model Context Protocol
-
ai_oca_mcp 16.0 (pull request #68) — OCA ↩︎
-
ai_oca_mcp_oauth 16.0 (pull request #133) — OCA ↩︎
-
mcp-server-odoo — ivnvxd ↩︎
-
mcp-server-odoo releases — ivnvxd
-
mcp-server-odoo OAuth (pull request #53) — ivnvxd
-
mcp_server (Odoo Apps) — much. Consulting ↩︎
-
muk_mcp_oauth (Odoo Apps) — MuK IT ↩︎
-
rag_odoo_mcp_server (Odoo Apps) ↩︎