The direct answer
Does Odoo Online support MCP? Not directly. Odoo Online — the official cloud SaaS plan where every instance lives on a *.odoo.com subdomain — blocks custom server-side modules, so a module-based MCP server simply can't be installed on it. Since nearly every "Odoo MCP" integration on the market ships as an Odoo module, that rules them all out on SaaS.
But that is not the end of the story. You can connect AI to Odoo Online — you just have to do it with an external MCP gateway that talks to your instance over its standard XML-RPC API instead of installing code inside Odoo. That is the architecture that makes Odoo Online AI integration possible, and the rest of this article explains why and how.
Why Odoo Online can't run an MCP module
Odoo Online is a shared, multi-tenant SaaS platform. To keep every customer's instance stable and secure on that shared infrastructure, Odoo does not let you upload or install custom server-side modules on a *.odoo.com instance. You get the standard apps from the Odoo App Store and configuration options — but no arbitrary server code.
A Model Context Protocol server that runs inside Odoo is, by definition, a custom module: it hooks into Odoo's internals and needs server-side access. That means an installed MCP module is structurally impossible on Odoo Online — not a bug, not a missing feature, but a deliberate platform boundary. This is true even for KSROlabs' own native MCP Server for Odoo: it is built for self-hosted, Odoo.sh, and on-premise Odoo, and it cannot be installed on a *.odoo.com instance either.
What's ruled out — and what actually works
Once you understand the SaaS module restriction, the options sort themselves neatly into two piles:
✗ Ruled out on Odoo Online
Any module-based "Odoo MCP" app that installs inside Odoo — including App Store modules and custom-built modules. If a solution asks you to install something on your Odoo server, it cannot run on a *.odoo.com instance.
✓ Works on Odoo Online
An external MCP gateway that runs outside Odoo and connects through the standard XML-RPC API — the same external interface Odoo has exposed and kept stable since Odoo 8. XML-RPC is a door Odoo Online leaves open on purpose, so an external bridge stays entirely within the SaaS rules.
How KSROlabs solves it: the Odoo Online MCP Gateway
KSROlabs pioneered the Odoo Online MCP Gateway — the first purpose-built, enterprise-grade way to connect AI to Odoo Online. It is an external gateway that runs entirely outside Odoo and connects Claude, ChatGPT, Cursor, and any MCP client to your live *.odoo.com data over XML-RPC. Nothing is installed inside Odoo, so there is no SaaS policy to conflict with — it authenticates with your Odoo credentials and translates Model Context Protocol tool calls into governed XML-RPC reads and opt-in writes.
Connecting an AI agent to a live ERP demands careful access control, so the gateway is security-first by design:
Read-only by default — the create_record, update_record, and delete_record write tools stay disabled until you explicitly opt in, and each change requires a confirmation step.
Bearer-token authentication protects the endpoint, so only clients holding your token can reach the gateway.
Configurable rate limits and payload size caps prevent runaway or accidental mass operations.
Model allowlisting and field-level access control let you restrict exactly which Odoo models and fields agents can see.
Full audit logging records every tool call, with optional error redaction so sensitive details never leak into your logs.
It is a fully managed, commercial product: KSROlabs provisions, configures, and operates a dedicated gateway for your instance, so there is no infrastructure for you to run. Once connected, your team can ask questions like "list this month's overdue invoices over $5,000" or "which deals closed last week?" straight from Claude, ChatGPT, or Cursor.
Odoo Online vs self-hosted: two different answers
The right answer depends entirely on how your Odoo is hosted. If you run self-hosted, Odoo.sh, or on-premise Odoo, those deployments do allow custom modules — so you can install the native MCP Server for Odoo module directly inside your instance. No external gateway needed.
If you run Odoo Online (SaaS) on *.odoo.com, the module route is closed, and the Odoo Online MCP Gateway is the purpose-built external bridge for you. These are two separate products for two different hosting models — pick the one that matches your deployment, or use both if you run a mixed environment.
Running Odoo Online and want AI access to your live data? Book a demo and we'll scope your instance and share pricing, or explore the Odoo Online MCP Gateway for the full feature set.
Frequently asked questions
Does Odoo Online support MCP servers?
Not directly. Odoo Online — the official cloud SaaS plan where every instance lives on a *.odoo.com subdomain — does not allow installing custom server-side modules, and nearly every "Odoo MCP" integration is a module. So a module-based MCP server cannot run on Odoo Online. You can still connect AI to Odoo Online, but you have to do it with an external MCP gateway that talks to your instance over XML-RPC instead of installing code inside Odoo.
Can I install an MCP module on Odoo Online?
No. Odoo Online blocks custom server-side module installation by design, which keeps the shared SaaS platform stable and secure. That restriction applies to every module-based MCP integration on the market, including KSROlabs’ own native MCP Server for Odoo. If you need AI access on a *.odoo.com instance, the working architecture is an external gateway, not an installed module.
How do I connect Claude or ChatGPT to Odoo Online?
Use an external MCP gateway. KSROlabs pioneered the Odoo Online MCP Gateway — a purpose-built, enterprise-grade bridge that runs outside Odoo and connects Claude, ChatGPT, Cursor, and any Model Context Protocol client to your live Odoo Online data over the standard XML-RPC API. Nothing is installed inside Odoo; the gateway authenticates with your Odoo credentials and translates MCP tool calls into governed XML-RPC reads and opt-in writes.
Is it secure to connect AI agents to live Odoo Online data?
Yes, when the gateway is built for it. The Odoo Online MCP Gateway is read-only by default — the write tools stay disabled until you explicitly opt in, and each change requires a confirmation step. It layers on Bearer-token authentication, configurable rate limits and payload caps, model allowlisting, field-level access control, and full audit logging, so you stay in control of exactly what agents can see and do.
What about self-hosted Odoo — does that support MCP?
Yes. If you run self-hosted Odoo, Odoo.sh, or on-premise, you can install the native MCP Server for Odoo module directly inside your instance — those deployments allow custom modules, so the gateway is not required. Odoo Online (SaaS) is the deployment that cannot install modules, which is why it needs the external gateway instead. These are two separate products for two different hosting models.
What does the Odoo Online MCP Gateway cost and how do I get it?
The Odoo Online MCP Gateway is a commercial, purpose-built product from KSROlabs, provisioned and managed by our team rather than downloaded and self-run. Book a demo or talk to sales and we will scope your instance, agree on a plan, and stand up a configured gateway for you. Contact us for current pricing.