“Odoo 20 forces its paid AI on you.” The phrase has circulated widely on LinkedIn in recent days, and it is half true. Odoo 20’s built-in AI is now paid for in credits, with no personal key possible. But Odoo 20 can also talk to your AI, the one you already use: Claude, ChatGPT or Grok, thanks to the MCP protocol. Here is what we found in the source code, how to connect it, and what it does not do.
1. What is true: the built-in AI moves to credits
In Odoo 19, the AI settings offered a “Enable custom OpenAI API key” box: you connected your own OpenAI account and paid OpenAI directly. In Odoo 20, this setting has gone. All the built-in AI functions (drafting, agents, call summaries…) go through the Odoo AI service and consume IAP credits, bought from Odoo.
For an SME that wanted to keep control over its AI provider, this is a real change.
💡 Key takeaway
Odoo 20’s built-in AI is paid for in Odoo AI credits, with no alternative. That is not the case with MCP.
2. What MCP changes: Odoo becomes a source for your AI
MCP (Model Context Protocol) is a standard that lets an AI assistant query external software. Odoo 20 Enterprise ships with an MCP server (ai_mcp module), which installs automatically with the AI app. It responds at the address https://votre-odoo/mcp.
In practice, you type “Who are my top 5 customers this quarter?” into Claude or ChatGPT, and the assistant fetches the answer from your Odoo database, live, with no export from the day before. The reasoning is done by the AI you have chosen: in this module we found no call to the Odoo AI service and no credit consumption.
💡 Key takeaway
With MCP, it is your Claude or ChatGPT subscription that does the work. It is still paid, but you are no longer limited to the built-in AI.
3. How to connect it: two paths
Path 1: one-click authorisation (OAuth). In your assistant, you add a connector with the /mcp address of your Odoo. On first connection, Odoo displays an authorisation page titled “Grant Access”, with two buttons, “Allow” and “Deny”, and the choice of how long access lasts (one day, one month, one year; the administrator can also choose “no limit”). These labels are not translated in V20: you will see them in English.
Only declared assistants can obtain this token. By default, Odoo 20 accepts claude.ai, chatgpt.com and grok.com. The list is managed in Settings > General Settings, “MCP OAuth” setting (not translated). The “Allow Dynamic Client Registration (DCR)” option, which would let any client register itself, is disabled by default: leave it that way.
Path 2: the API key. For a tool that does not handle OAuth, each user can generate a key: My profile > Security tab > API Keys > “Add API Key”, with the “MCP” scope. Odoo then displays the server address and the Authorization: Bearer … header to copy (box in English). Odoo itself reminds you: this key must never be shared, and is only pasted into a password-type field.
💡 Key takeaway
Nothing connects without the user’s explicit consent, and that consent has an expiry date.
4. What the AI can see, and what it cannot do
The assistant acts with the rights of the logged-in user. A salesperson who cannot see the accounting in Odoo will not see it any more through Claude. By default, Odoo exposes five tools, all marked read-only: list of models, list of fields, search, grouping (totals by customer, by month…) and starting context (user, time zone, companies).
The administrator can open up more: a server action ticked “Available in MCP” becomes a tool the AI can call, and the “Readonly Tool” box indicates whether it only reads. An action that writes, exposed to an AI, deserves serious thought about safeguards.
💡 Key takeaway
Your Odoo rights apply to the AI. By default, it reads; it only writes if you have decided so.
⚔️ The Match: Odoo 20’s built-in AI vs your AI via MCP
| Criterion | Built-in AI (Odoo AI) | Your AI via MCP |
|---|---|---|
| Who does the reasoning | The Odoo AI service | Claude, ChatGPT or Grok |
| How it is billed | Odoo AI credits, no personal key | Your assistant subscription |
| Where you ask the question | In Odoo | In the tool you already use |
| Writing to the database | Depends on the function used | Read-only by default |
| Built into Odoo screens | Yes | No: everything goes through the chat |
Comparison based on reading the Odoo 20 Enterprise source code (ai and ai_mcp modules), October 2026.
5. Prerequisites and limits
- Odoo 20 Enterprise: the ai_mcp module does not exist in Community.
- A public HTTPS address: it is Claude’s or ChatGPT’s servers that call your Odoo. An instance reachable only from your internal network will not be reachable.
- Your data passes through the assistant: what the AI reads is sent to its provider. Weigh this against your privacy policy and the GDPR, especially for HR or health data.
- The AI can get a query wrong: an important figure should be checked in Odoo before it is announced in a meeting.
It is mainly useful to managers who already use Claude or ChatGPT and want to query their figures without opening a report: overdue invoices, projects going off track, top customers.
💡 Key takeaway
The right approach: start with a user with limited, read-only rights, then widen from there.
The Verdict: Odoo 20 charges for its AI, but lets you plug in your own
MCP does not replace the built-in AI: it gives you a choice. You still have to decide who connects, with what rights and for which questions. That is exactly the kind of scoping we do in an
Odoo process audit, and pass on to your teams in
Odoo training.
Already using Claude or ChatGPT at work? We will show you how to connect it to your Odoo.
“Odoo 20 forces its paid AI on you.” The phrase has circulated widely on LinkedIn in recent days, and it is half true. Odoo 20’s built-in AI is now paid for in credits, with no personal key possible. But Odoo 20 can also talk to your AI, the one you already use: Claude, ChatGPT or Grok, thanks to the MCP protocol. Here is what we found in the source code, how to connect it, and what it does not do.
1. What is true: the built-in AI moves to credits
In Odoo 19, the AI settings offered a “Enable custom OpenAI API key” box: you connected your own OpenAI account and paid OpenAI directly. In Odoo 20, this setting has gone. All the built-in AI functions (drafting, agents, call summaries…) go through the Odoo AI service and consume IAP credits, bought from Odoo.
For an SME that wanted to keep control over its AI provider, this is a real change.
💡 Key takeaway
Odoo 20’s built-in AI is paid for in Odoo AI credits, with no alternative. That is not the case with MCP.
2. What MCP changes: Odoo becomes a source for your AI
MCP (Model Context Protocol) is a standard that lets an AI assistant query external software. Odoo 20 Enterprise ships with an MCP server (ai_mcp module), which installs automatically with the AI app. It responds at the address https://votre-odoo/mcp.
In practice, you type “Who are my top 5 customers this quarter?” into Claude or ChatGPT, and the assistant fetches the answer from your Odoo database, live, with no export from the day before. The reasoning is done by the AI you have chosen: in this module we found no call to the Odoo AI service and no credit consumption.
💡 Key takeaway
With MCP, it is your Claude or ChatGPT subscription that does the work. It is still paid, but you are no longer limited to the built-in AI.
3. How to connect it: two paths
Path 1: one-click authorisation (OAuth). In your assistant, you add a connector with the /mcp address of your Odoo. On first connection, Odoo displays an authorisation page titled “Grant Access”, with two buttons, “Allow” and “Deny”, and the choice of how long access lasts (one day, one month, one year; the administrator can also choose “no limit”). These labels are not translated in V20: you will see them in English.
Only declared assistants can obtain this token. By default, Odoo 20 accepts claude.ai, chatgpt.com and grok.com. The list is managed in Settings > General Settings, “MCP OAuth” setting (not translated). The “Allow Dynamic Client Registration (DCR)” option, which would let any client register itself, is disabled by default: leave it that way.
Path 2: the API key. For a tool that does not handle OAuth, each user can generate a key: My profile > Security tab > API Keys > “Add API Key”, with the “MCP” scope. Odoo then displays the server address and the Authorization: Bearer … header to copy (box in English). Odoo itself reminds you: this key must never be shared, and is only pasted into a password-type field.
💡 Key takeaway
Nothing connects without the user’s explicit consent, and that consent has an expiry date.
4. What the AI can see, and what it cannot do
The assistant acts with the rights of the logged-in user. A salesperson who cannot see the accounting in Odoo will not see it any more through Claude. By default, Odoo exposes five tools, all marked read-only: list of models, list of fields, search, grouping (totals by customer, by month…) and starting context (user, time zone, companies).
The administrator can open up more: a server action ticked “Available in MCP” becomes a tool the AI can call, and the “Readonly Tool” box indicates whether it only reads. An action that writes, exposed to an AI, deserves serious thought about safeguards.
💡 Key takeaway
Your Odoo rights apply to the AI. By default, it reads; it only writes if you have decided so.
⚔️ The Match: Odoo 20’s built-in AI vs your AI via MCP
| Criterion | Built-in AI (Odoo AI) | Your AI via MCP |
|---|---|---|
| Who does the reasoning | The Odoo AI service | Claude, ChatGPT or Grok |
| How it is billed | Odoo AI credits, no personal key | Your assistant subscription |
| Where you ask the question | In Odoo | In the tool you already use |
| Writing to the database | Depends on the function used | Read-only by default |
| Built into Odoo screens | Yes | No: everything goes through the chat |
Comparison based on reading the Odoo 20 Enterprise source code (ai and ai_mcp modules), October 2026.
5. Prerequisites and limits
- Odoo 20 Enterprise: the ai_mcp module does not exist in Community.
- A public HTTPS address: it is Claude’s or ChatGPT’s servers that call your Odoo. An instance reachable only from your internal network will not be reachable.
- Your data passes through the assistant: what the AI reads is sent to its provider. Weigh this against your privacy policy and the GDPR, especially for HR or health data.
- The AI can get a query wrong: an important figure should be checked in Odoo before it is announced in a meeting.
It is mainly useful to managers who already use Claude or ChatGPT and want to query their figures without opening a report: overdue invoices, projects going off track, top customers.
💡 Key takeaway
The right approach: start with a user with limited, read-only rights, then widen from there.
The Verdict: Odoo 20 charges for its AI, but lets you plug in your own
MCP does not replace the built-in AI: it gives you a choice. You still have to decide who connects, with what rights and for which questions. That is exactly the kind of scoping we do in an
Odoo process audit, and pass on to your teams in
Odoo training.
Already using Claude or ChatGPT at work? We will show you how to connect it to your Odoo.