As an Odoo Implementation Partner, you run AI across a dozen client Odoo instances, not one. We build an MCP tool tailored for you.
Why use an MCP in the first place
If you are a serious Odoo implementation partner, a lot of the work is still manual. You migrate data by hand-mapping spreadsheets, write migration scripts, check a client's configuration in a custom module or in Odoo Studio. The AI you already pay for, Claude or ChatGPT, cannot see the client's Odoo, so you copy data into a chat, paste the answer back, and hope nothing sensitive went with it. An MCP server closes that gap. It brings Odoo to your favourite AI tool, so it reads and changes the real data instead of guessing.
The catch for partners
You are never working in one database. You run ten, or twenty, on different versions, some on Odoo.sh, some on Odoo Online, each with its own login. And most Odoo MCP servers are a module you install inside the client's Odoo, keep updated, and pay for per database. On Odoo Online you cannot install modules at all, so a chunk of your clients are out before you start. For the rest, every new client is another install, another licence, and another thing to retest when they upgrade. Ten clients, ten of everything.
We went the other way. You connect to a client's Odoo with an API key or OAuth, and the server runs on our side. Nothing lives in their database. Point it at whichever database you want, a client's production, a staging copy, or a dev instance, so you can try it somewhere safe before you go near live data. Online clients connect the same way as Odoo.sh ones. Adding a client takes about five minutes, and moving between them is a dropdown, not a fresh login. It works on Odoo v14 through v19, Community and Enterprise, so an older client is not a special case.
The work you actually do all day
The unglamorous parts of an implementation are where this earns its keep. Import and migrate data without mapping every field by hand. Clean up duplicates and adjust Studio configuration by asking, instead of clicking through screens. When you are building custom modules, Claude Code can read and write the instance you are working in while it codes, so you are not copying record IDs back and forth between windows.
It does more than read and write. It can press the same buttons you would, confirm an order, post an invoice, mark a lead lost, and run those across a batch of records when that is the job. Attachments work too. All of it goes through your own API key, so what the key cannot do, the AI cannot do either. And if you track delivery in Project and Timesheets, you can log the hours from the same chat.
What Odoo partners say
More than 1,500 people have connected their Odoo, and they use it every week. A few of them:
"We've been running it against our own Odoo for a while, and it's the cleanest way to bring AI inside Odoo for our clients."
Ivan Nordgaimer, Akarigo
"Love love love your tool."
Andrew Law, Odoo It Yourself
Where it runs, and whether it is safe
Everything goes through your own API key and its permissions, so the AI inherits exactly what you can already do, nothing more. We host in the EU and encrypt at rest. If you would rather weigh the hosting options yourself, including running it on your own machine, we wrote up where to host your Odoo MCP server.
It is free to start, no credit card. Connect one client and see what it does to your week.