AI Agent & MCP for Odoo Community

An AI assistant and an MCP server, both served by Odoo itself.

What it does

AI Agent & MCP for Odoo Community adds an assistant that answers questions about your own records through a controlled set of tools, and makes the same Odoo instance an MCP server that external AI clients can connect to as a specific Odoo user.

You bring your own provider key. You are billed directly by the provider, and nothing is routed through a CODEerts service.

The part that matters is where the security lives. It is enforced by Odoo, not by the prompt. Every tool call runs as the requesting user, so access rights, record rules and company rules apply exactly as they do in the web client. The assistant cannot delete or archive records, change access rights, read credentials, run Python or SQL, execute server actions, or call arbitrary methods, because no such tool exists for it to call.

Three execution modes decide how much the agent may do without being asked. Read Only searches, reads and reports, and never writes. Assisted runs low-risk writes automatically while a short fixed list of sensitive operations stops and waits for a person. Autonomous runs the create and update actions it has been permitted.

When something does stop for approval, the pending action shows what was asked for, what it would do, and the exact field values, with an Approve or Reject decision. Nothing is written until someone chooses.

A per-agent permission table grants read, create or update per model. A model that is not listed cannot be reached at all, which makes the boundary something you can read off one screen rather than infer from a prompt.

On the MCP side, Odoo is the server. There is no Node process, no separate daemon and no external gateway to operate. Tokens are personal and scoped: each user mints their own, each token maps to one real Odoo user, and each carries its own execution policy.

Every tool call is recorded, refusals included, so the activity log shows what the agent did and what it was stopped from doing.

Who it's for

Teams on Odoo Community who want an assistant over their own data without handing that data to a hosted middleman, and who need the answer to "what can it actually touch" to be a permission table and an approval queue rather than a promise about a prompt.

It also suits anyone connecting an external AI client over MCP who needs each token to be traceable to one real Odoo user with that user's permissions, rather than a shared integration account.