The short answer
An Odoo implementation partner can put AI access in front of client data using the MCP Server for Odoo. It is a normal Odoo module: you install it in the client database, create a scoped API key, and the client's Claude, ChatGPT or Cursor can read live Odoo data through it.
The part that actually shapes a partner deployment is the boundary: there is one server per database, and no shared endpoint across a portfolio. That is not a missing feature. A single credential that reached into several client databases would be exactly the wrong thing to hand an AI agent, and it is the first thing a client's security review would object to.
Deploying across client databases
Each client database gets its own install, its own MCP endpoint and its own credentials. In practice partners managing a portfolio script the install as part of their standard provisioning and keep one credential per client, the same way they already handle any other module and any other API key.
What that buys you is a clean story for each client: their key, their permission scope, their audit log, revocable from their own Odoo without a call to you. The trade is that there is no single pane of glass across the portfolio — you are managing N deployments, not one. For most partners that is the correct trade, but it is worth knowing before you scope the work. The mechanics are covered in full on multi-database Odoo MCP.
Mixed portfolios: self-hosted, Odoo.sh and Odoo Online
Partner portfolios are rarely all on one hosting model, and the hosting model decides the architecture. Self-hosted, on-premise and Odoo.sh clients allow custom modules, so they get the module. Odoo Online clients do not allow custom server-side modules at all, so no module-based MCP server can run there — including ours — and those clients get the Odoo Online MCP Gateway instead, which runs outside Odoo and connects over the standard external API.
If a prospect is on *.odoo.com and someone has told you a module will work there, it will not. That is worth checking early — it is the single most common reason an Odoo AI project stalls after the sale. The background is in does Odoo Online support MCP?
What the client controls after handover
Access is bounded by the Odoo permissions of the user the integration runs as, and the API key is generated inside the client's own Odoo. So the client can narrow the scope, rotate the key or revoke it outright from their own instance, without involving you and without anything routing through KSROlabs.
Reads work by default. Writes are governed separately and are not implicit — which is usually the answer a client's finance or security lead is looking for when they ask what the AI is allowed to change. The detail is in the Odoo MCP security guide and in MCP governance for Odoo.
Partner questions
Can Odoo partners deploy the MCP Server for client databases?
Yes. The MCP Server for Odoo is a native Odoo module, so an implementation partner installs it in a client database the same way as any other module — through the Apps list on self-hosted, Odoo.sh or on-premise deployments. Each client database gets its own install, its own API keys and its own audit log. There is nothing partner-specific to configure and no central console to sign into first.
How does a partner cover several client databases?
One server per database. The MCP Server lives inside a single Odoo database, so covering several clients means one install per database, each exposing its own MCP endpoint with its own scoped API keys, permissions and audit log. There is no shared cross-database endpoint, and that is deliberate — a single credential spanning multiple client databases would break the permission boundary that makes AI access safe to grant in the first place. Partners managing many databases usually script the install and keep one credential per client.
What about clients on Odoo Online?
Those need the gateway, not the module. Odoo Online (the *.odoo.com SaaS plan) blocks custom server-side modules, so no module-based MCP server can be installed there — ours included. For those clients the Odoo Online MCP Gateway runs outside Odoo and connects over the standard external API instead. Most partner portfolios are mixed, so in practice it is the module for self-hosted and Odoo.sh clients and the gateway for Odoo Online ones.
Can a client revoke AI access without involving the partner?
Yes, and this matters for the handover conversation. The API key is generated inside the client’s own Odoo and is bounded by the permissions of the Odoo user it runs as, so the client can narrow its scope or revoke it entirely from their own instance at any time. Nothing routes through KSROlabs, and nothing depends on the partner staying in the loop.
Does each client database need its own licence?
The MCP Server is a one-time purchase from the Odoo App Store per deployment, with no per-seat or per-call subscription. Free setup support is included. If you are deploying across a portfolio of client databases rather than a single instance, get in touch before you buy — that is a conversation worth having directly rather than working it out from the listing.
Is there a partner or reseller programme?
Not a published one with fixed tiers. We work with Odoo partners, agencies and integrators case by case, including managed deployment where KSROlabs installs and maintains the server inside the client’s Odoo environment. Tell us what your portfolio looks like and what you need to be able to promise your clients, and we will tell you plainly whether we can support it.