I built the bridge between Claude and Odoo — so your ERP answers real questions and takes safe, approved actions in plain English, not just stores data.
Most attempts to bolt AI onto an ERP take one of two shapes, and I have watched both fall short the same way. The first exports data into a general-purpose chatbot that has no idea what today's actual stock level is — a snapshot, not a system. The second embeds a chat widget that can only paraphrase a help article back at you. Neither approach knows who is allowed to see what, and neither can safely change a record, so the AI stays a novelty for drafting emails instead of becoming a tool that actually touches sales, finance or inventory.
The gap I set out to close is a connection that runs inside the ERP itself, obeys the same access rules as the person logging in, and knows the difference between answering a question and changing one. That is what I built: an MCP server that lives inside Odoo and lets Claude speak to it directly.
Here is what that connection actually does, capability by capability.
A secure connector lets Claude query live sales, CRM, inventory, accounting and project data directly through Odoo's own business logic — no CSV exports, no stale snapshots. Trend, ranking, pivot and funnel questions get aggregated on the server, so you get back an actual number with a clickable link to the source record, not a guess stitched together from a handful of rows.
The assistant never runs as a superuser. Each connection is mapped to one real Odoo login, so the same access rights, record rules and field-level security that apply to that person inside Odoo apply automatically to what the AI can see and touch — one person's assistant can never surface data that person was never allowed to read.
Simple creates and edits happen immediately and land in a draft state, exactly as if a person had typed them. Anything higher-risk — confirming an order, posting an invoice, cancelling a transfer, deleting a record — stops and shows a plain-English preview of exactly what will change. Only an explicit approval commits it, and every AI-made change is tagged in the record's own history, so nothing happens invisibly.
Saved, repeatable workflows turn a multi-step report — trend, top customers, pipeline conversion, then a written narrative — into a single request that runs the same way every time. Results can also be published as a live KPI page with its own shareable link, so a manager or an outside stakeholder without an Odoo login can see current numbers refreshed on every visit.
An optional semantic index lets the assistant find the record someone is thinking of even when they can't recall its exact name, re-checking every result against the asker's permissions before it's shown. A separate per-person memory lets someone state a reporting preference once — a currency, an exclusion, a default filter — and have it respected in every session after.
Teams connect with a one-click sign-in instead of pasting a secret. Each connection can be scoped to a business area with its own rate limit and expiry, and every call — tool, arguments, records touched, outcome — lands in an audit log with its own dashboard, including attempts that were denied. The connector runs inside Odoo itself, so it upgrades cleanly across major versions instead of breaking against an external integration layer.
This isn't a bolt-on limited to one corner of the system. The connector currently reaches these areas of Odoo — each one still governed by the same access rules as the login it's connected to, not a separate integration account with permissions of its own:
I'm Muhammad Salman Ali Khan, an Odoo Techno-Functional Consultant in Dubai and Head of Projects at Techbot Information Technology LLC. Ten-plus years in Odoo and 100+ implementations sit behind this, along with certification across six versions — an explicit list, not a range: Odoo v13, v14, v15, v16, v18 and v19. I built this connector because I wanted my own clients' Odoo systems to answer questions the way a good analyst would, not the way a chatbot pretending to be one does.
If you're weighing whether to move to a version that supports this kind of work, I've written a full breakdown of what actually changed in the platform itself.
I'm Muhammad Salman Ali Khan, an Odoo Techno-Functional Consultant in Dubai and Head of Projects at Techbot Information Technology LLC, a UAE Odoo partner — 10+ years, 100+ implementations, certified across Odoo v13, v14, v15, v16, v18 and v19. Tell me what you'd want to ask your ERP and I'll give you a scoped, honest view of what connecting it to Claude actually involves — at no cost.
Get a free business evaluation