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, checking every record so nothing is lost. 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.
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.
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.