Loading page
MCP Server for Odoo
by TechnoVision · Odoo App
A token speaks for a person, not for the database.
The Model Context Protocol is how a client like Claude Desktop discovers and calls tools on a server. This makes your Odoo one of those servers, with the same permission model as the assistant inside Odoo - because it is literally the same code.
One-off licence per Odoo instance. The store bills in its own base currency, so checkout may differ by a few cents.
- Odoo 18
- Community & Enterprise
- Requires AI Assistant for Odoo
- Version 18.0.1.0.0 · 2026-09-07
Security Center
Live82
Score
1.2k
Events / 24h
3
Alerts
Export volume · 14 days
Unusual export detected
res.partner · 4,812 rows · outside business hours
Illustrative UI. Product screenshots to be dropped into this frame.
What it does
The difference between an MCP server you can install and one you cannot
A token is bound to one user
Every request runs through with_user(that person). A token belonging to somebody who cannot see payroll cannot be talked into showing it.
Tools scoped per request
tools/list returns only what that person can reach, so a client is never even told that a tool it cannot use exists.
The secret is never stored
A SHA-256 digest and a short non-secret prefix. Shown once at issue, unrecoverable - which is what makes a stolen backup much less bad than a stolen token.
A generated client configuration
The wizard hands you the JSON block to paste, with the URL and header already correct, because the commonest failure is a token in the wrong field.
The same audit trail
Every read over MCP appears alongside the reads made in Odoo, marked with its source, its token and the client’s self-reported name.
Expiry and revocation
One click, effective on the next request. The audit rows survive it, because the interesting question is usually asked afterwards.
Screenshots
Product gallery
3 captures of the shipped product: tokens, and who each speaks for, issued once, with the configuration, what a client has been reading.
Tokens, and who each speaks for
Issued once, with the configuration
What a client has been reading
How it works
Installed in minutes, useful the same day
- 1
Install it alongside the assistant
It adds one route and a Connections menu. No token exists until you issue one.
- 2
Issue a token
Name it, choose who it speaks for, set an expiry. Odoo shows the token once with the client configuration.
- 3
Paste it into your client
Restart the client and your Odoo tools appear in its list.
- 4
Watch what it reads
Filter the audit trail to MCP. Every call, with the token that made it.
FAQ
Questions we get asked
No. The underlying tool layer has no write, create, delete or method call, so there is nothing to expose.
You can, and you should not. Every answer would be read with one person’s rights and the audit trail would credit them with everybody’s questions.
Revoke it. It stops working on the next request, and the audit rows survive so you can see what it read while it was live.
No. Tools are what an ERP has to offer; the rest would be surface area with nothing behind it.
The Apps Store prices a module together with what it requires. This one needs AI Assistant for Odoo, so the listing shows $118 - $49 for this plus $69 for the assistant. If you already own the assistant you are not charged for it twice.
Get MCP Server for Odoo
Install from Odoo Apps, or talk to us about a guided rollout across multiple companies.