How to connect Claude to Odoo
with an MCP server

Why connect Claude to Odoo?

Odoo holds critical business data — sales orders, invoices, CRM leads, inventory levels, purchase history. But extracting insight from that data typically requires: custom reports, SQL queries, or manual data exports.

When you connect Claude to Odoo, you can query all of this with natural language. "Show me the top 10 customers by revenue this quarter." "Which invoices are overdue by more than 30 days?" "Create a draft quote for Acme Corp based on last month's order."

The KSROlabs MCP Server for Odoo makes this possible — securely, with full Odoo permission enforcement and audit logging for every AI action.

What you need before you start

Step-by-step setup guide

Follow these 6 steps to go from a fresh Odoo instance to a working Claude + Odoo integration.

If the connection fails at this point, the message tells you which step to go back to: "Authorization failed" means the token, while connecting but seeing no tools means the token worked and the key simply has no model access yet. Every documented error is indexed under troubleshooting.

Does the Odoo edition matter?

Community and Enterprise both work, and neither gives Claude anything the other does not. The MCP Server is a standard Odoo module and it enforces the same access rules either way, so an Enterprise licence is not a prerequisite for connecting Claude.

Hosting is the decision that actually matters. Odoo.sh, self-hosted and on-premise instances allow custom modules, so the module installs and the endpoint is served by Odoo itself. Odoo Online — any instance on a *.odoo.com address — does not allow custom server-side modules at all, so no MCP module can run there, from us or anyone else. That is a platform boundary, not a licensing upsell, and it catches people out constantly. If you are on Odoo Online you need an external gateway instead: the full explanation is here, and the Odoo Online MCP Gateway is the product that covers it.

Odoo versions 14.0 through 20.0 are supported. On the Claude side, connecting a custom MCP connector in the hosted apps (claude.ai, Teams, Enterprise) needs a paid Claude plan; Claude Desktop and Claude Code connect through local configuration without one.

What Claude can do once connected

Once configured, Claude has access to 8 MCP tools that cover every key Odoo operation:

What it looks like day to day

The first week is mostly people testing whether it really knows their data. Expect questions they already know the answer to — last month's revenue, a specific customer's open orders — because that is how anyone builds trust in a new tool. Let that happen. It is also how you find out that a domain filter is narrower than you meant.

After that it settles into a pattern: the questions that were never worth a report. Which quotes went quiet this month, whether a supplier's lead times have slipped, what changed in the pipeline since Friday. Questions somebody would have asked an analyst for, or more often, would simply not have asked.

Two things worth setting expectations on. Claude reads what the key is scoped to and nothing else, so an answer that looks wrong is usually an answer that is correctly narrow — check the scope before you doubt the data. And a read-only key is the right default for the first month: write access is easy to add once people trust the reads, and awkward to walk back if an agent creates something nobody expected.

Common mistakes, and what causes them

Four failures account for most of the support we see on a first connection. None of them takes long to fix once you know which one you are looking at.

1. Connecting before granting model access. The client connects, reports no error, and lists no tools — so it looks broken when it is working exactly as designed. The whitelist is default-deny, so a key with no models exposes nothing. Grant the models, then reconnect.
2. Pasting a token that was rotated. Rotation invalidates the previous version immediately, so a client configured before the rotation fails with an authorization error and no obvious cause. The audit log names the exact reason.
3. Registering the wrong redirect URI. OAuth refuses to redirect anywhere that was not registered in advance, and the match is exact — scheme, host, path and trailing slash. Claude and ChatGPT each have their own callback URL.
4. Giving write access on day one. Not an error message, just a decision that is hard to reverse. Start read-only, watch the audit log for a few weeks, then widen deliberately.

Every error we have documented, with its cause and fix, is indexed under troubleshooting.

Security best practices

Connecting an AI agent to your ERP requires careful access control. Follow these practices:

Frequently asked questions