User guide
How to use MCP Server for Odoo, screen by screen.
What this gives you
Your Odoo becomes a server that an MCP client - Claude Desktop, or anything else speaking the protocol - can ask questions of. The answers are exactly what the person the token speaks for could have got by asking inside Odoo.
Connecting
- AI Assistant > Connections > Issue a token.
- Copy the configuration block it gives you into your client.
- Restart the client so it picks up the new server.
Your client should now list the tools your Odoo offers. There is one search tool - and, where totals are allowed, one count tool - per exposed model.
What the tools look like
Tool names are derived from the model: search_res_partner, count_account_move. Their descriptions come from the What this is line on each exposure, so a clear line there produces better tool choices.
What a session looks like
You: Which customers still owe us money? The client calls count_account_move, then search_account_move. Claude: Nine customers have unpaid documents, $265,575.00 outstanding...
Every one of those calls appears in Odoo under AI Assistant > Audit > What the assistant read, marked as coming from an MCP client, with the token that made it.
What it will not do
- Write anything. There is no write, create, delete or method call to expose.
- Reach data the token's person cannot. A tool for a model they cannot read is never listed, and calling it by name anyway is refused.
- Tell you what it cannot see. Records outside that person's access are absent from results, not marked as withheld.
Two people, two tokens
Issue one token per person. A shared token means every answer is read with one person's rights and the audit trail says so - which is the thing this module exists to avoid.
Checking what a client has been reading
AI Assistant > Audit > What the assistant read, filter From an MCP client. Group by person or by model. Refusals are kept: a refused call is the enforcement working.