Odoo MCP on Community: skip the Custom-plan gate if you run the module.
Community is not the thing that blocks MCP. Odoo Online Standard is. Self-hosted Community can run an in-Odoo MCP module and never touch /json/2. An external proxy still needs an API.
Community vs Online Standard
People mix “Community is free so there is no API” with “Online Standard has no external API.” The first is false on self-hosted Community — XML-RPC/JSON-2 are there. The second is Odoo’s commercial term on Online. API cost · Community vs Enterprise.
Odin’s MCP suite is Community and Enterprise, 18 and 19. In-process ORM means you are not buying Custom just to let Claude read invoices.
When Community still needs JSON-2
If you refuse to install a module and run MCP as a sidecar, you are back on the external API. On 19 that should be JSON-2. On 18/17, XML-RPC. MCP vs JSON-2.
Hosting: self-hosted · Odoo.sh (sh is an Enterprise/Custom story) · Enterprise.
Apps Store versus source install
Community shops install from the Apps Store or from git. Either way, test MCP on a copy: OAuth, a real Claude connector, a denied write. Community is not a reason to skip staging.
OPL-1 modules (including ours) have licence terms. Read them. Hosting that includes the module is a different SKU than buying the zip once.
Community + Online is not a thing
Odoo Online is Enterprise-shaped SaaS. If someone said “we’re on Community Online,” they mean something else — odoo.sh trial, a partner host, or confusion. MCP advice follows the actual host, not the slogan.
FAQ
Does Community include the external API?
Self-hosted yes. Odoo Online Standard no — that is a plan, not the Community codebase.
Odin on Community?
Yes, 18 and 19.
Need Enterprise for MCP?
No, not for an in-Odoo module on Community.
Keep going
Start read-only. Ask a real question.
Sandbox on sample Odoo 19 data, or we put MCP on your instance.