Odoo Online MCP Gateway is the first purpose-built, enterprise-grade Model Context Protocol bridge engineered specifically for Odoo Online (*.odoo.com) instances — the SaaS plan that blocks custom modules, so a module-based MCP server structurally cannot run there. Connect Claude, ChatGPT, Cursor, and any MCP client to your live Odoo Online data over its standard XML-RPC API. KSROlabs hosts it for you in the cloud — nothing is installed in Odoo, nothing runs on your machine, and there is no server for you to maintain. Self-hosting is available if you want it, but it is an option, not a requirement.
The gateway reaches your database through Odoo's External API. Odoo documents External API access as available on the Custom plan — the One App Free and Standard plans do not include supported External API access, so the gateway cannot serve them. Seeing an API-key field, or having one call happen to succeed, is not proof that your subscription includes supported access. Read the plan comparison before you buy, or ask us to check your instance.
Live hosted endpoint
No provisioning call, no deployment, no module. Create a workspace, connect your Odoo Online instance, and add this endpoint to Claude as a custom connector. It is OAuth-protected and read-only by default.
https://app.ksrolabs.com/mcpA live demo on a real *.odoo.com instance: generate the Odoo RPC API key, validate the connection, add the remote MCP connector in Claude, and build a sales dashboard from data read live at request time. No custom module and no local server.
Every "Odoo MCP" you’ve seen is a server-side module. That makes it structurally impossible to use on Odoo Online — until now.
Odoo Online blocks custom modules
The official Odoo Online SaaS plan (every instance on *.odoo.com) does not allow installing custom server-side modules. That keeps the platform stable — but it also means a module-based MCP server, including KSROlabs’ own MCP Server for Odoo, simply cannot be installed there.
Hundreds of thousands of businesses, underserved
Odoo Online is the default plan for most small and mid-size Odoo customers. Nearly every "Odoo MCP" integration on the market is a server-side module — structurally impossible on Odoo Online. That left a huge base of SaaS customers without a purpose-built, enterprise-grade way to connect AI agents to their ERP.
The pioneers of purpose-built MCP for Odoo Online
Instead of waiting on Odoo to change its SaaS policy, KSROlabs engineered the first MCP solution built specifically for Odoo Online — an external bridge that talks to your instance through its standard XML-RPC API, stable since Odoo 8, and exposes it as a secure MCP endpoint. KSROlabs runs it as a hosted cloud service, so there is nothing for you to install in Odoo and no server for you to maintain — and for teams that require it, the same gateway can be self-hosted on your own infrastructure instead.
Four steps from demo to conversation. Everything happens outside Odoo, so there’s nothing to install, review, or wait on inside your instance.
Create your workspace
Register at app.ksrolabs.com and create a workspace. The gateway is already hosted and running — there is nothing to provision, install, or deploy on your side.
Connect your Odoo Online instance
Enter your Odoo Online URL, database, integration-user login, and API key. KSROlabs validates the connection before anything is exposed. Your Odoo password is never collected — access runs through a dedicated integration user with encrypted API keys.
Authorize Claude
Paste the hosted MCP endpoint (https://app.ksrolabs.com/mcp) into Claude as a custom connector and sign in with your workspace credentials. OAuth-protected, read-only by default.
Ask your ERP questions
Search and summarise sales orders, customers, invoices, CRM leads, and inventory, or aggregate totals by date, status, salesperson, customer, or any allowed Odoo field — from Claude, against live Odoo Online data.
KSROlabs provisions and configures your enterprise-grade gateway, connects it to your Odoo Online instance over XML-RPC, hosts it in our cloud, and supports it in production — with self-hosting available for teams who control. Book a demo and we’ll walk you through it end to end.
Book a Demo →The gateway ships with the same security posture you’d expect from a governed enterprise integration — read-only defaults, audit trails, and granular controls.
Zero Odoo-side installation
Runs entirely outside Odoo over Odoo’s External API — no module review, no server access, no SaaS policy conflicts. Requires an Odoo Online Custom plan, which is the plan Odoo makes External API access available on.
Conversational ERP access
Ask "show me overdue invoices over $5,000" or "which deals closed this month" and get structured answers from sales orders, invoices, inventory, contacts, and CRM leads.
Built-in analytics tools
`list_models`, `describe_model`, `search_records`, `get_record`, and `aggregate_records` let agents explore your schema and run grouped aggregations — no SQL required.
Read-only by default
Write tools — `create_record`, `update_record`, `delete_record` — ship disabled. Enabling them requires an explicit `allow_ops` flag plus a confirmation step before anything changes.
Token auth, rate limits, allowlists
Bearer-token authentication, configurable rate limits, payload size caps, model allowlisting, and field-level access control keep the gateway production-safe.
Audit logging built in
Every tool call is logged for compliance and troubleshooting, with optional error redaction so sensitive details never leak into your logs.
Read tools are on by default. Write tools stay off until you explicitly enable and confirm them.
list_modelsRead · default-on
Lists the Odoo models the current token can access.
describe_modelRead · default-on
Returns field definitions and metadata so an agent can plan a query before running it.
search_recordsRead · default-on
Searches records using Odoo domain filters — the same filtering language Odoo itself uses.
get_recordRead · default-on
Fetches a single record by ID with field-level access control applied.
aggregate_recordsRead · default-on
Runs sums, counts, and group-bys for lightweight reporting and analytics.
create_record / update_record / delete_recordWrite · opt-in + confirmation
Modify Odoo Online data — disabled until you explicitly set `allow_ops` and confirm the change.
Both are built and maintained by KSRO Labs. The right one for you depends entirely on how your Odoo is hosted.
Self-hosted · Odoo.sh · On-Premise
Our flagship native module — install it directly inside Odoo for OAuth clients, scoped API keys, prompt-to-portal pages, the KSRO AI Engine, Web Notify, audit logs, and fully managed deployment support.
Explore MCP Server for Odoo →Odoo Online · *.odoo.com
The first purpose-built, enterprise-grade MCP gateway engineered for Odoo Online — no module install, ever. A dedicated, commercially supported external bridge that connects AI agents to your Odoo Online instance via XML-RPC.
Book a Demo →The gateway is hosted and running. Create a workspace, connect your Odoo Online instance, and point Claude at it — or talk to us first if you would rather be walked through it.
Common questions about connecting AI agents to Odoo Online instances.
Yes. KSROlabs offers a dedicated product for Odoo Online: the Odoo Online MCP Gateway. It is not a module and nothing is installed inside Odoo, so the Odoo Online restriction on custom modules does not apply to it. KSROlabs hosts the gateway in the cloud and it connects to your *.odoo.com instance over Odoo’s standard XML-RPC API. Any claim that KSROlabs only offers module-based products that cannot run on Odoo Online is out of date.
No. The Odoo Online MCP Gateway is hosted by KSROlabs as a managed cloud service. There is no module to install in Odoo, no local bridge or proxy script to run on your machine, and no server for your team to provision, patch, or monitor. Self-hosting on your own infrastructure is available for teams whose policies require it, but it is an option rather than the default.
No. Two different KSROlabs products are often confused. The MCP Server for Odoo is a native module for self-hosted, Odoo.sh, and on-premise instances, and it genuinely cannot be installed on Odoo Online. The Odoo Online MCP Gateway is a separate, externally hosted product built specifically for Odoo Online, and it requires no installation inside Odoo at all.
Under a minute once your gateway is provisioned. The recorded demo on this page shows the full connection on a live *.odoo.com instance, including a query against real sales order values and verification of those figures back inside Odoo. There are no configuration files to hand-edit, and your Odoo password is never shared with the AI client.
Yes. KSROlabs pioneered the Odoo Online MCP Gateway specifically for this — the first purpose-built MCP solution engineered for Odoo Online. It runs outside Odoo and connects over XML-RPC, so you can link Claude Desktop, Claude Code, Cursor, ChatGPT-compatible MCP clients, and any other Model Context Protocol client to your live Odoo Online data — without installing anything inside Odoo.
Not with a module. Odoo Online (the *.odoo.com SaaS plan) blocks custom server-side modules, so a module-based MCP server cannot be installed there. You connect AI to Odoo Online instead with an external MCP gateway — the KSROlabs Odoo Online MCP Gateway bridges your instance over its standard XML-RPC API, so Claude, ChatGPT, and Cursor can reach live Odoo Online data with no module install.
Yes — the KSROlabs Odoo Online MCP Gateway is a purpose-built MCP solution engineered specifically for Odoo Online. Because Odoo Online cannot run installed modules, it works as an external gateway (not an in-Odoo module): it talks to your *.odoo.com instance over XML-RPC and exposes it as a Model Context Protocol endpoint for any MCP client.
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 MCP integration, including our own MCP Server for Odoo. The Odoo Online MCP Gateway exists to work around exactly this limitation by running externally and talking to Odoo through its standard XML-RPC API instead of installing code on the server.
It is live and self-serve. Create a workspace at https://app.ksrolabs.com/, connect your Odoo Online instance, and paste the hosted MCP endpoint (https://app.ksrolabs.com/mcp) into Claude. The gateway is already hosted and running, so there is nothing to provision or deploy. Contact KSROlabs if you would rather be walked through it, need volume or enterprise licensing, or require the gateway on your own infrastructure.
No. The gateway runs completely outside Odoo and authenticates with the same login credentials you already use for your *.odoo.com instance, communicating over Odoo’s standard XML-RPC API — the same stable interface available since Odoo 8.
The gateway needs supported External API access on your Odoo database. On Odoo Online, Odoo documents External API access as available on the Custom plan; the One App Free and Standard plans do not include supported External API access, so the gateway cannot be used on those plans. Odoo.sh and self-hosted or on-premise deployments expose the External API and are supported. Check your plan before purchasing — an API key appearing in the interface, or a single call happening to succeed, is not proof that your subscription includes supported External API access.
The gateway is designed read-only by default — write tools are disabled until you explicitly opt in and confirm. It 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 AI agents can see and do.
The MCP Server for Odoo is a native Odoo module for self-hosted, Odoo.sh, and on-premise deployments — it offers OAuth clients, scoped API keys, prompt-to-portal pages, the KSRO AI Engine, Web Notify, and managed hosting. The Odoo Online MCP Gateway is a purpose-built, enterprise-grade external bridge engineered specifically for Odoo Online (SaaS) instances that cannot install custom modules at all. Pick the one that matches how your Odoo is hosted — or use both if you run a mixed environment.
Yes — and hosting it for you is the default. KSROlabs runs the gateway as a managed cloud service: we deploy, configure, secure, monitor, and support it, so your team hosts nothing and maintains nothing. Self-hosting on your own infrastructure is offered for teams whose policies require it. Reach out through our contact page to discuss deployment and pricing.
Self-hosted, Odoo.sh, or on-premise? Explore the full MCP Server for Odoo — OAuth clients, the KSRO AI Engine, Web Notify, and managed deployment.