Short answer: Cledoo MCP runs on Odoo.sh and On-Premise. It cannot run on Odoo Online (SaaS). This isn’t a Cledoo restriction — it’s how Odoo’s own hosting tiers are built. Odoo Online is a managed, standardized environment that does not accept custom or third-party modules. If your Odoo is on Odoo Online today and you want AI access to your data, you have two paths, and this article lays them out plainly.
Can I run Cledoo MCP on Odoo Online?
No. Odoo’s own hosting comparison page states it directly: Odoo Online is “Odoo standard (no customizations)” and “Odoo apps only (no third-party apps)” — meaning no custom Python modules, ever, regardless of vendor. This applies to every custom module, not just Cledoo MCP. It’s a platform-level restriction Odoo enforces to keep its managed SaaS environment stable and uniform across every tenant.
Can I run Cledoo MCP on Odoo.sh?
Yes. Odoo.sh is Odoo’s own cloud platform built specifically to host custom code.
You push modules through a Git repository (or as submodules for third-party code),
and Odoo.sh builds, tests, and deploys them across staging and production
branches. Cledoo MCP installs there exactly like it would on-premise: upload the
module, install it from Apps, and it exposes /mcp under your existing user
permissions.
Can I run Cledoo MCP on-premise?
Yes, and this is the simplest case technically. On-premise means you (or your
hosting partner) run the Odoo server, so you have full filesystem access to the
addons path. Odoo’s documentation is explicit here too: on-premise supports
“customization possible (on existing apps or to create new apps)” and
“third-party application installation possible.” Copy the Cledoo MCP module into
your addons directory, restart the server, install it from Apps — done.
Why does Odoo Online block custom modules at all?
Odoo Online is a multi-tenant SaaS: thousands of databases running on shared infrastructure that Odoo itself patches, upgrades, and secures. Letting arbitrary third-party Python code run inside that environment would mean Odoo can no longer guarantee stability, security, or predictable upgrades for every customer sharing that infrastructure. So the trade a customer makes for Odoo Online’s “zero maintenance” simplicity is: no custom code, full stop. Odoo Studio can still get you as far as new fields, views, and simple automations built from the UI — but that’s not the same as installing a Python module, and it can’t install an MCP server.
Cledoo MCP hosting compatibility
| Hosting type | Can install Cledoo MCP? | Why |
|---|---|---|
| Odoo Online (SaaS) | No | Odoo blocks all custom/third-party modules on this tier — a platform rule, not a Cledoo one |
| Odoo.sh | Yes | Built by Odoo specifically to run custom modules, via Git-based deployment |
| On-Premise | Yes | Full server access — install any module, including Cledoo MCP |
I’m on Odoo Online — what are my options?
If AI-over-Odoo matters enough to act on, you have two realistic paths:
- Migrate to Odoo.sh. This is usually the least disruptive move: same Odoo Enterprise licensing model, same managed-cloud convenience, but with a Git-based deployment pipeline that accepts custom modules. Odoo provides built-in migration tooling from Online to Odoo.sh.
- Move to on-premise. More control, but more operational responsibility — you (or a hosting partner) own the server, backups, and updates. Makes sense if you already have IT infrastructure or need this data to stay entirely inside your own network.
Either way, the module itself doesn’t change. Cledoo MCP Classic installs the same way — from the Apps Store or by uploading the module file — once you’re on a hosting tier that allows it.
Does this affect Cledoo MCP Pro too?
Yes, identically. Both Classic (free) and Pro (€189 one-time) are the same kind of artifact — a custom Odoo module — so the hosting rule applies equally to both. There’s no SaaS-compatible version to fall back to, because the constraint sits at the Odoo platform level, not in what Cledoo built.
The takeaway
Before evaluating any AI-over-Odoo tool, check your hosting tier first — it decides whether custom modules are even possible. Odoo Online: no. Odoo.sh and On-Premise: yes, both fully compatible with Cledoo MCP. If you’re not sure which tier you’re on, it’s visible in your Odoo subscription or database manager, and your Odoo partner (or Odoo support) can confirm it in minutes.