The problem: Odoo Online blocks the module that everyone else ships
If you run Odoo Online — the official cloud SaaS plan where every instance lives on a *.odoo.com subdomain — and you have tried to connect an AI agent to it, you have probably hit a wall. Nearly every "Odoo MCP" integration on the market is a server-side Odoo module. And Odoo Online, by design, does not let you install custom server-side modules.
That restriction is what keeps the shared SaaS platform stable and secure — but it also means a module-based Model Context Protocol server is structurally impossible on Odoo Online. This is true even for KSROlabs' own native MCP Server module: it is built for self-hosted, Odoo.sh, and on-premise Odoo, and it cannot be installed on a *.odoo.com instance either.
So when people search for "connect Claude to Odoo Online" or "MCP for Odoo Online", they find guides that quietly assume they can install a module — and none of them work on SaaS. Countless businesses on Odoo Online are stuck. The rest of this guide explains the breakthrough architecture that does work, and how KSROlabs pioneered it.
The breakthrough: an external XML-RPC bridge, not a module
KSROlabs pioneered the Odoo Online MCP Gateway — the first purpose-built solution for connecting Claude, ChatGPT, Cursor, and any MCP client to Odoo Online. It is a game-changing, enterprise-grade bridge, and its key architectural decision is that it runs entirely outside Odoo. Nothing is installed on the *.odoo.com server, so there is no SaaS policy to conflict with.
Instead of hooking into Odoo's internals like a module would, the gateway talks to your instance through Odoo's standard XML-RPC API — the same external interface Odoo has exposed and kept stable since Odoo 8. Every Odoo Online instance already speaks XML-RPC. The gateway authenticates with your Odoo credentials, then translates Model Context Protocol tool calls from your AI client into XML-RPC reads and (opt-in) writes.
That is why the architecture works on SaaS where modules cannot: XML-RPC is an externaldoor Odoo Online leaves open on purpose, whereas modules require server-side access Odoo Online deliberately locks down. The result is a governed MCP endpoint to your live Odoo Online data — the definitive commercial gateway for the SaaS platform.
How it works: the architecture at a glance
The gateway sits between your AI client and Odoo Online. The data path is simple and fully governed at every hop:
Your AI client (Claude / ChatGPT / Cursor) → secured MCP endpoint (Bearer-token auth) → KSROlabs gateway (policy + access control) → Odoo XML-RPC API → your live *.odoo.com data
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 are 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.
A recommended practice is to bind the gateway to a dedicated, least-privilege Odoo user rather than an admin account, so agents inherit only the access that user has. Once connected, your team can immediately ask questions like "list this month's overdue invoices over $5,000" or "which deals closed last week?"
Why a purpose-built gateway matters
It is possible to bolt together a generic script that pokes at Odoo's XML-RPC API and calls it an integration. In practice that approach breaks down the moment you put it near real ERP data: no confirmation gates on writes, no field-level controls, no audit trail, and no answer when something goes wrong. Generic tooling treats Odoo as just another database. It is not.
Because KSROlabs pioneered MCP for Odoo Online, the gateway is engineered specifically around how Odoo models, access rights, and business logic actually behave — and around the operational realities of letting an AI agent touch a live ERP. That is the difference between a proof of concept and an enterprise-grade solution you can put in front of your team with confidence.
KSROlabs is not the only vendor in this space — alternatives such as Pantalytics also serve Odoo Online. What sets the Odoo Online MCP Gateway apart is that it is a dedicated, purpose-built commercial product with the security posture, model governance, and managed operations that production ERP integrations require.
Getting started: book a demo
The Odoo Online MCP Gateway is a managed, commercial solution — KSROlabs provisions and operates a dedicated gateway for your instance, so there is no infrastructure for you to run. Getting live takes three steps.
Book a demo with KSROlabs
Get in touch with the KSROlabs team for a walkthrough of the Odoo Online MCP Gateway. We show you how AI agents query your live *.odoo.com data, discuss your models and access requirements, and share pricing for a managed deployment.
We provision and configure your gateway
KSROlabs provisions and configures a dedicated, enterprise-grade gateway for your Odoo Online instance. We wire it to your *.odoo.com database over the standard XML-RPC API — nothing is installed inside Odoo — and set your read/write policy, model allowlist, and field-level access controls.
Connect Claude, ChatGPT, or Cursor
Point Claude Desktop, Claude Code, Cursor, or any Model Context Protocol client at your secured MCP endpoint using the Bearer token we issue. Then ask questions about your live Odoo Online data in plain English.
Ready to connect AI to your Odoo Online data? Talk to sales for pricing and a managed deployment, or explore the Odoo Online MCP Gateway product page for the full feature set.
Frequently asked questions
Can I connect Claude to Odoo Online (SaaS)?
Yes. The Odoo Online MCP Gateway from KSROlabs runs outside Odoo and connects to your *.odoo.com instance over the standard XML-RPC API. That lets you link Claude Desktop, Claude Code, Cursor, ChatGPT-compatible MCP clients, and any other Model Context Protocol client to your live Odoo Online data — with nothing installed inside Odoo.
Why can't I install an Odoo MCP module on Odoo Online?
Odoo Online — the official cloud SaaS plan hosted on *.odoo.com — does not allow installing custom server-side modules. That restriction applies to every module-based "Odoo MCP" integration on the market, including KSROlabs' own MCP Server for Odoo. A gateway that runs externally and talks to Odoo over XML-RPC is the architecture that makes AI access possible on Odoo Online.
How do I get access, and what does it cost?
The Odoo Online MCP Gateway is a commercial, purpose-built solution from KSROlabs. Access is 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.
Is it secure?
Yes. The gateway is read-only by default — the write tools (create_record, update_record, delete_record) stay disabled until you explicitly opt in, and each change requires a confirmation step. It also layers on Bearer-token authentication, configurable rate limits, payload size caps, model allowlisting, field-level access control, and full audit logging, so you stay in control of exactly what agents can see and do.
How is this different from the self-hosted MCP Server module?
The MCP Server for Odoo is a native module for self-hosted, Odoo.sh, and on-premise deployments — it cannot be installed on Odoo Online. The Odoo Online MCP Gateway is an external bridge purpose-built for SaaS instances that cannot install modules, connecting to *.odoo.com over XML-RPC. If you run self-hosted Odoo, the module is the right fit; if you run Odoo Online, the gateway is built for you.
Can I connect ChatGPT and Cursor to Odoo Online the same way?
Yes. The gateway speaks the standard Model Context Protocol over stdio and HTTP, so any MCP-compatible client works — Claude, Cursor, Claude Code, and ChatGPT-compatible MCP clients included. The setup is identical: point the client at your gateway endpoint with the Bearer token we issue.