The problem: you run Odoo Online, and Claude can't see it
You want to connect Claude to Odoo Online. Your ERP lives on a *.odoo.com subdomain, your sales orders, invoices, CRM pipeline, and stock levels are all in there — and you want to ask Claude about them in plain English instead of building reports by hand. The catch: Claude has no idea your Odoo instance exists until something bridges the two.
On self-hosted or Odoo.sh Odoo, the usual answer is a server-side module that adds Model Context Protocol support directly inside Odoo. But Odoo Online — the official cloud SaaS plan — does not let you install custom modules. That restriction keeps the shared platform stable, but it also means the standard module route to a Claude Odoo Online integration is structurally off the table. Guides that tell you to install an "Odoo MCP" module simply do not apply to a *.odoo.com instance.
So how do you get Claude Desktop, claude.ai, or Claude Code talking to live Odoo SaaS data without a module? That is exactly what the rest of this guide covers.
The solution: the Odoo Online MCP Gateway
KSROlabs pioneered the Odoo Online MCP Gateway — a purpose-built, enterprise-grade external gateway that bridges Odoo Online to Claude. 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 — and no module to maintain.
The gateway connects to your instance through Odoo's standard XML-RPC API — the external interface every Odoo Online instance already exposes — and presents a secured MCP endpoint that Claude can use. When you ask Claude a question, it calls MCP tools on the gateway, the gateway translates them into governed XML-RPC reads (and opt-in writes) against your live database, and Claude answers with your real data. That is what makes a Claude Odoo SaaS integration possible where a module never could be.
How to connect Claude to Odoo Online
The gateway is a managed product, so getting live is onboarding rather than a self-install. Three steps take you from a *.odoo.com instance to Claude answering questions about it.
Request your Odoo Online MCP Gateway
Contact KSROlabs to onboard onto the Odoo Online MCP Gateway. We scope your *.odoo.com instance, agree on the models Claude should reach, and provision a dedicated, managed gateway wired to your database over Odoo's XML-RPC API — nothing is installed inside Odoo.
Add the gateway MCP endpoint to Claude
We issue a secured MCP endpoint URL and a Bearer token. Add it to Claude Desktop (Settings → Developer → Edit Config), to claude.ai as a custom connector, or to Claude Code — whichever Claude surface your team uses. Claude discovers the available Odoo tools automatically.
Ask Claude about your live Odoo Online data
Open a new Claude conversation and ask in plain English: "List this quarter's top customers by revenue" or "Show overdue invoices over $5,000." Claude queries your live *.odoo.com data through the gateway and answers with real numbers.
For Claude Desktop, the config we help you add looks something like this — an MCP server entry pointing at your gateway endpoint with the Bearer token we issue:
{
"mcpServers": {
"odoo-online": {
"url": "https://gateway.ksrolabs.com/mcp/your-instance",
"headers": {
"Authorization": "Bearer YOUR_GATEWAY_TOKEN"
}
}
}
}The exact values are provisioned for your instance — this snippet is illustrative. On claude.ai you add the same endpoint as a custom connector, and Claude Code takes the endpoint through its MCP configuration. One gateway, every Claude surface.
What you can ask Claude once connected
With the gateway live, your team queries Odoo Online in natural language — no report builder, no CSV exports. A few examples of what Claude can answer against your live *.odoo.com data:
Sales
"List this quarter's top 10 customers by revenue" or "Which quotations over $10k are still open?"
Invoices
"Show invoices overdue by more than 30 days" or "What's our total unpaid balance this month?"
Inventory
"Which products are below reorder level?" or "How many units of SKU-204 are on hand?"
CRM
"Summarise the deals that moved stage this week" or "Who are my highest-value open leads?"
Security: what Claude can and can't touch
Letting an AI client reach a live ERP demands careful access control, so the gateway is security-first by design. You decide exactly what Claude can see and do on your Odoo Online data:
Read-only by default — write tools stay disabled until you explicitly opt in, and each change requires a confirmation step before it reaches Odoo.
Bearer-token authentication protects the MCP endpoint, so only Claude clients holding your token can reach the gateway.
Model allowlisting and field-level access control restrict exactly which Odoo models and fields Claude can query.
Configurable rate limits and payload caps prevent runaway or accidental mass operations against your instance.
Full audit logging records every tool call Claude makes, with timestamp and payload, for compliance and debugging.
Bind the gateway to a dedicated, least-privilege Odoo user so Claude inherits only that user's access — never your admin account.
Running self-hosted or Odoo.sh instead?
This guide is specifically for Odoo Online (*.odoo.com), where modules cannot be installed. If you run self-hosted, Odoo.sh, or on-premise Odoo, you can install the native MCP Server for Odoo module directly — it runs inside your instance and is the right fit for those deployments.
For the full walkthrough of the module route, see Connect Claude to Odoo (self-hosted). And if you want a broader overview of connecting any AI client — ChatGPT and Cursor included — to Odoo Online, read Connect AI to Odoo Online.
Frequently asked questions
Can I connect Claude to Odoo Online (SaaS)?
Yes. Because Odoo Online (*.odoo.com) blocks custom server-side modules, you connect Claude through the KSROlabs Odoo Online MCP Gateway — an external bridge that talks to your instance over Odoo's XML-RPC API and exposes an MCP endpoint Claude can use. Nothing is installed inside Odoo, so it works on the SaaS plan where module-based integrations cannot.
Does Claude Desktop / claude.ai work with Odoo Online?
Yes. Claude Desktop, claude.ai (as a custom connector), and Claude Code all speak the Model Context Protocol. Point any of them at the gateway's MCP endpoint with the Bearer token we issue and Claude can read your live Odoo Online data. The same endpoint serves every Claude surface — there is no separate setup per app.
Do I need to install an Odoo module?
No. Odoo Online does not allow custom module installation, so no module is involved. The gateway runs entirely outside Odoo and connects over the standard XML-RPC API that every *.odoo.com instance already exposes. If you run self-hosted or Odoo.sh Odoo instead, the native MCP Server module is the right fit — see our guide on connecting Claude to self-hosted Odoo.
Is it secure to give Claude access to Odoo Online data?
Yes. The gateway is read-only by default — the write tools stay disabled until you explicitly opt in, and each change requires confirmation. It adds Bearer-token authentication, configurable rate limits, model allowlisting, field-level access control, and full audit logging, so you control exactly what Claude can see and do. Binding it to a least-privilege Odoo user is recommended.
How do I get it and what does it cost?
The Odoo Online MCP Gateway is a commercial, managed product from KSROlabs — provisioned and operated by our team rather than downloaded and self-run. Book a demo or contact sales and we will scope your *.odoo.com instance, agree on a plan, and stand up a configured gateway connected to Claude. Contact us for current pricing.
What is the difference between this and 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 XML-RPC bridge purpose-built for *.odoo.com SaaS instances. If you run Odoo Online, the gateway is the path to Claude; if you run self-hosted Odoo, use the module.