Odoo, set up by your agent - end to end.
Zoxron MCP is the automation side of Zoxron. Give your AI agent a temporary, scoped key and it installs, configures, secures, backs up and upgrades Odoo on a server you own - one step at a time, showing you exactly what it will do before it does it.
Standing up Odoo the right way is a long checklist - a hardened server, the database, TLS, a reverse proxy, backups that actually restore, monitoring, then the upgrades that come every year. Zoxron MCP hands that checklist to your AI agent as a set of safe, ordered tools. You talk to the agent in plain language; it does the work on your server and reports back. Nothing that changes anything runs without showing you first.
For the people who put Odoo on servers.
Partners & consultants
Deploying Odoo for clients, repeatably.
The same clean deployment every time, on any provider - bring your own Enterprise .deb, keep your own cloud account. Your agent does the runbook; you keep the judgement.
Teams on their own Odoo
Self-hosted, without the DevOps.
Run Odoo on your own box and stay in control, without hiring for the server side. Backups, TLS, monitoring and upgrades become something you ask for, not something you dread.
Anyone starting fresh
Odoo without the weekend.
No Odoo, no server yet? The agent can recommend and create the machine, then take it all the way to a running, backed-up, monitored install - and hand you the keys.
The whole lifecycle, not just install.
Server, database, Odoo (Community or your Enterprise), a reverse proxy and TLS - on a server you already have or one the agent creates for you.
Not a script that exits zero - a real restore drill into a scratch database, so you know the backup actually works before you need it.
Move to a newer major version, or switch Community to Enterprise - and it carries your custom, OCA and Odoo Studio customizations across the jump, with record counts checked against a baseline. Backup-first, one major at a time, the original kept as an instant rollback.
Private on-box monitoring with push alerts, staging copies to test on, and a go-live that refuses to flip until acceptance checks pass.
Odoo 20, Community and Enterprise, is supported: installed natively or in Docker on Ubuntu 24.04. Coming from 19? Your data moves with its full history into a new Odoo 20 database and is compared with the original before you switch, while your 19 stays as the way back. Once Odoo’s official upgrade service takes 19 to 20, it can carry the data instead, and everything around the data stays the same.
Odoo moves your data. We move your system.
A new Odoo version is more than a converted database. Your custom modules, your Studio changes, your settings and the access each person has must arrive too, and someone has to show that they behave the same. Zoxron MCP moves all of it, with proof.
Odoo’s official upgrade service when it covers your versions and your Enterprise subscription. When it does not, from Odoo 19 to 20, your full history moves into a new database: accounting with reconciliations, numbering that continues, stock, manufacturing, chatter, files, and users who keep their passwords.
Custom modules ported to the new version and installed on a test database first. Fields, views and automations built in Studio found, carried across and checked.
A test copy runs next to production. Every person is compared on the old and the new version: the same records, menus, settings and reports. A data check alone can pass while a screen fails.
A rehearsed switch with a known duration, scheduled jobs and integrations switched on deliberately, and the old system kept ready as the way back.
A large manufacturing company moved from Odoo 19 to 20 Enterprise: 55 custom modules ported, about 670,000 rows across some 600 data models proven equal, about 20,000 files carried over, every user checked again on the new version. How it went
The runbook we run for ourselves - handed to your agent.
Every step in Zoxron MCP is one we do on real deployments: patch the box, install the deps the .deb omits, prove the restore, size the workers, lock down the admin. We turned that discipline into tools an agent can drive, with the dangerous steps gated in code - destructive actions only on a fresh box, go-live only after checks, a preview before every change.
Zoxron runs its own site, ERP, academy and mail on this exact tooling, self-hosted on our own servers. Zoxron MCP is not a slide about what we could build - it is how we keep our own systems running, opened up for you to drive. Our own ERP already runs on Odoo 20 Enterprise, moved there the same way the agent offers you: a new database, the data carried over and compared, the old system kept as the way back.
The portal is for everyone.
Get an access token, point your agent at it, and deploy your first Odoo. The guide walks the whole path; the first steps are read-only, so you can look before you touch anything.
Straight talk: Zoxron MCP is free and it’s a solo, founder-run project - which is exactly why every destructive step is gated in the code and previewed before it runs. Even the custom code that needs adjusting for a new version is rewritten by your AI agent, which explains each change and asks you only when there’s a real choice; a genuinely huge, deeply-bespoke system can still be worth your own developer’s look, and importing data from other systems is still on the way. No surprises.