Running Odoo properly is a long list of jobs: a secured server, the database, a domain with HTTPS, backups that actually restore, monitoring, and a version upgrade every year or so. Zoxron MCP hands that whole list to your AI agent, Claude, Codex or any other assistant that speaks MCP. You say what you want in plain language. The agent does the work on a server you own and tells you what it did. Here is what that covers, from an empty machine to an Odoo you can run your company on.

From an empty server to a running Odoo

Start with a server you already have, or with none at all. Give the agent a temporary, scoped key for your cloud account and it recommends a machine sized for your workload, sets it up and removes the key afterwards. The account stays yours.

Then it installs Odoo the way you choose:

  • Community or Enterprise. Community is fetched for you. For Enterprise you bring the package from your own Odoo subscription, and the agent checks it is the edition and version you asked for before it carries on.
  • Every current version, up to Odoo 20. Odoo 16 to 20 are supported, Odoo 20 in both editions.
  • Native or Docker. Native, from the official package as a system service, is the closest to standard and the simplest to back up. Docker gives each instance its own container, so several Odoo versions can run side by side on one server, for example 16 and 19.
  • One Odoo or several. Each instance gets its own domain, database and nightly backup, and adding one never touches the ones already running.

Along the way it installs every dependency your apps need, tunes Odoo to the size of the server, sets the admin password, creates the production database with the apps you picked, points your domain at the server and switches on HTTPS through Cloudflare or Let's Encrypt. What used to be a weekend of server work becomes a conversation.

Backups you have seen come back

A backup only counts if it restores. Nightly backups come with an automatic restore test into a scratch database, so you know they work long before the day you need one. Copies can also leave the server, to a machine you own or to S3-compatible object storage, and the agent checks those too. The full picture is in Backups, monitoring and a tested recovery.

A server that tells you when something is wrong

The agent installs private monitoring on your own server. The dashboard stays on the machine, never exposed to the internet, and you get a push alert the moment Odoo, PostgreSQL, the web server, the disk, memory or CPU has a problem. At any time you can ask your agent "how's my server?" and get a plain-language answer.

Going live is just as orderly. The switch happens once the acceptance checks pass, and you get a handoff document with everything the next person needs. Want a safe place to try something first? The agent makes a staging copy of production, with real emails off, scheduled jobs off and payments in test mode, and removes it when you are done.

Upgrades and moves with a completeness check

Upgrades are the job most Odoo owners put off. The agent moves you to a newer major version, Community or Enterprise, or from Community to Enterprise. It backs up first, goes one major version at a time, carries your custom add-ons, community (OCA) add-ons and Odoo Studio changes across the jump, and checks record counts against a baseline. Your current database stays as an instant rollback. Before you start, it scans your Studio customizations and points out the few that rely on a part of Odoo that changes, so only those need a look.

Moving to Odoo 20 works in the same careful way. Your business data goes into a new Odoo 20 database, and the agent compares both databases side by side, counts and content in every language, before you switch. Your Odoo 19 stays as the way back. What changes in 20 is covered in Odoo 20: what really changes before you move. Moving a live Odoo to a new server is handled too: the agent checks the new machine can take it, carries the database, files and custom add-ons across and switches the domain at cutover.

Help with your own modules

Custom code is where many Odoo systems keep their edge. The agent deploys your modules from a git repository: it tests a commit on staging and promotes it to production only when the tests pass, with production backed up first and rolled back automatically if anything breaks. When it writes or ports a module, it checks field names against a reference covering Odoo 17 to 20, so the code fits the version you run. And when you ask "can Odoo also do this?", it searches thousands of free community modules by what they do and shows you the ones released for your version.

You stay in control at every step

Every step that changes something is shown to you first, exactly as it will run, and waits for your yes. After each step the agent explains in plain language what it did, what to check next and where your backup is. An install ends with a summary: how to log in, which apps are in place and how the server is sized. You never have to read a server log to know where you stand. The portal, the guide and the full capabilities reference are available in English, Polish and German, and the agent has over 80 tools to work with.

Proof, not a promise

Zoxron runs its own website, ERP, academy and mail on exactly this tooling, on its own servers. Our ERP already runs on Odoo 20 Enterprise, moved there the way the agent offers it to you: a new database, the data carried over and compared, the old system kept as the way back. Every step in Zoxron MCP is one we take on real deployments, turned into tools your agent can drive.

FAQ

How do I start?

Create an account at zoxron.com/connect. In Claude Desktop or claude.ai you add a custom connector and sign in, with no token to copy. For Claude Code or Codex you take a named token. The first steps are read-only, so you can look at your server together with the agent before anything changes. Installing Odoo with Zoxron MCP is free.

Community or Enterprise?

Both, installed the same way. Community is free and fetched for you. Enterprise runs on your own Odoo subscription: you download the package, and the agent takes it from there. If you start on Community, you can switch to Enterprise later, backup-first like any upgrade.

Does my data stay with me?

Yes. Odoo runs on a server you own, in your own cloud account, and the backups go where you decide. Odoo is the tool your data is collected with. The data is what matters, and it stays yours: open, portable, never locked in.

See everything Zoxron MCP covers on the Zoxron MCP page, then connect your agent at zoxron.com/connect and put your first Odoo on your own server.