Everything, organised by the job you're doing
Connect an assistant to your Odoo, decide exactly what it may touch, host it yourself, migrate onto it, and control who inside the company sees what. Start with the product you installed, or jump to the task.
By product
Connect Claude or ChatGPT to Odoo
The connector itself: install it, copy one URL, and paste it into your assistant. Every request runs as the signed-in Odoo user, read-only until you say otherwise.
The AI apps, together
What the MCP server and AI Dashboards do, and how dashboards get built by asking the assistant you already connected.
Access control, enforced server-side
Record and field-level permissions without writing XML — and enforced underneath the API, not just hidden in the interface.
Two-way Shopify sync
Products, inventory, orders and customers moving both directions, with payout reconciliation.
Connect your assistant
One server URL works for every client below — the protocol is the same. Pick the one you actually use.
Claude
Settings → Connectors, paste the URL, sign in with your Odoo login.
ChatGPT
Connectors under Developer Mode. Plan requirements explained.
Gemini
Streamable HTTP and the allowed_tools allow-list.
Claude Desktop
The desktop app rather than the web client.
Cursor
One-click install into the editor.
Claude Code
Driving Odoo from the terminal.
What MCP actually is
Deciding what the AI may touch
The default scope is read-only. Everything here is about widening it deliberately rather than by accident.
The four gates
OAuth consent, your governance scope, the per-model matrix, and the user's own Odoo rights.
Running read-only
What a read-only assistant can and cannot do, and when to widen.
Security model
Where the boundaries are enforced, and what the audit trail records.
Whose credentials does it use?
Why a connector should never have its own ERP login — and what running as the user costs.
Row caps and truncated answers
For anyone building an MCP server: why a capped result becomes a confidently wrong answer.
When the install succeeds but nothing works
Five post-install failures, none of which raised an error.
Install, host and migrate
Your assistant has to be able to reach your Odoo over public HTTPS. Which hosting you are on decides whether you can install a module at all.
Self-hosted
Running MCP inside Odoo, which skips the external-API question entirely.
Odoo Online
Plan limits, the Custom-plan API gate, and what Online will not let you install.
Odoo.sh
Git-based hosting, and the different path for custom modules.
Install Odoo 19 Community
A clean install from scratch.
Docker install
Odoo and Postgres in containers.
Migrate off Odoo Online
Moving a live database onto your own server.
Backup and restore
Database and filestore, and why both have to travel together.
Let us deploy it
One-click provisioning onto a server we manage, preconfigured for your trade.
Who inside the company sees what
This is the layer underneath everything above — an assistant can never exceed the permissions of the person using it, so these are the permissions that decide the ceiling.
Access rights management
Groups, model access and record rules, and how they combine.
Field-level security
Hide, lock or mask a field so it holds over the API too.
User permissions
Assigning what an individual can reach.
Multi-company access
Company boundaries, and how they apply to AI requests too.
Hide fields by group
The task-shaped version, with the clicks.
Limit employee permissions
Narrowing a role without breaking the person's day.
A live Odoo, no signup
Rather than reading about the settings, open them. The sandbox runs on sample data and resets itself.
sandbox.odin.ist/odoo/settings#mcp_governance_suite
Login admin · Password admin
Ask a person
If a guide here doesn't cover it, or something behaves differently to how this is written, tell us — that is usually a documentation bug on our side.