The short answer
The module is listed on the Odoo App Store for 20.0. Nothing about the setup changes: the endpoint is still served by Odoo itself, API keys and model access still live in Odoo records, and an upgrade from 19 carries the configuration with it. Test it on staging first, as you would with any module through a major version change.
The more interesting change is that Odoo 20 now has native MCP, which means for the first time there is a real choice to make on a current version.
Which one you need
Odoo's native MCP is enough when
You are on Odoo 20, people are asking questions and reading reports, and nobody will later need an answer to "which agent read which records, and when". It is capable as shipped — 27 documented tools — and it costs nothing extra to try.
You need the governed module when
You are on Odoo 14–19, where native MCP does not exist; or you need OAuth with per-user consent, rate limiting, a full audit log, and the ability to revoke one agent without disturbing the others; or you are on Odoo Online, where no module installs at all and the route is an external gateway.
Frequently asked questions
Does the KSROlabs MCP Server support Odoo 20?
Yes. The module is published on the Odoo App Store for version 20.0, alongside 14.0, 15.0, 16.0, 17.0, 18.0 and 19.0 — seven versions from one codebase. If you are upgrading from Odoo 19, the MCP setup moves with you: the endpoint, the API keys and the model access rules work the same way on 20.
Odoo 20 has its own MCP server. Do I still need a module?
For exploration, reporting and question-answering on Odoo 20, Odoo's own MCP server is a capable choice as shipped and we would not pretend otherwise. You need a separate module in three situations: you are on Odoo 14 through 19, where native MCP does not exist at all; you need governance Odoo's documentation does not describe, such as OAuth with per-user consent, rate limiting, an audit log of what each agent read, or revocation short of waiting for a key to expire; or you are on Odoo Online, where no module installs and an external gateway is the only route.
What happens to my MCP configuration when I upgrade to Odoo 20?
Treat it like any other module upgrade: test it on a staging copy before the production cutover. The configuration itself — API keys, model access, OAuth clients and scopes — carries across, because it lives in Odoo records rather than in files on disk. The one thing worth re-checking afterwards is model access on any custom models you added, since an upgrade is a common moment for model names and access rights to shift underneath an integration.
Can I run Odoo 20's native MCP and the KSROlabs module at the same time?
They serve different endpoints, so there is no technical conflict in having both installed. Whether you should is a governance question rather than a technical one: two MCP surfaces into one database means two sets of credentials, two permission models and two things to remember to revoke when someone leaves. If you are running the governed module for a reason, that reason usually argues for having one way in rather than two.