Odoo Oduflow
Oduflow — AI-First Odoo Development & CI
Provision an isolated, ephemeral Odoo environment for every git branch on Docker, and hand it to your AI coding agents over MCP — a closed feedback loop for fully autonomous, spec-driven Odoo development.
Not just another Odoo ERP connector
Most Odoo MCP servers connect an AI to your live ERP so it can read and write business records. Oduflow sits at the other end of the workflow: it helps agents build Odoo itself.
An agent writes module code, spins up a real Odoo instance, installs the module, reads the traceback, fixes the code, runs the tests, and clicks through the UI — all without a human relaying errors back and forth.
How it works — the closed feedback loop
┌──────────────────────────────────────────────────────┐
│ AI Agent │
│ (Cursor, Cline, Amp, Claude, …) │
└──────┬──────────────────────────────▲────────────────┘
│ 1. Read spec │ 5. Read errors,
│ 2. Write code │ fix code,
│ 3. Install module via MCP │ retry
│ 4. Click-test UI via │
│ Playwright / Agent Browser │
┌──────▼──────────────────────────────┴────────────────┐
│ Oduflow (MCP Server) │
│ • install_odoo_modules → traceback or success │
│ • run_odoo_tests → test pass/fail with details │
│ • get_environment_logs → runtime errors │
│ • upgrade_odoo_modules → upgrade output │
└──────────────────────────────────────────────────────┘
The MCP toolkit (54 tools)
- Environments —
create_environment,list/get/start/stop/restart_environment,delete_environment - Sync & build —
pull_and_apply(smart: decides install vs. upgrade vs. restart from the diff),install_odoo_modules,upgrade_odoo_modules - Verify & debug —
run_odoo_tests,get_environment_logs,run_odoo_shell,run_db_query - Code in place —
read_file_in_odoo,write_file_in_odoo,search_in_odoo,http_request_to_odoo - Templates —
save_as_template,import_template_from_odoo,refresh_template,list_templates - Infrastructure — auxiliary services (Redis, Meilisearch, Elasticsearch…), volumes, extra addon repos, git credentials
Why it's fast and isolated
- Reusable database templates — clone large production databases instantly via PostgreSQL templates + fuse-overlayfs. Environments share the template DB and filestore; only per-branch changes consume disk.
- One environment per git branch — fully isolated, ephemeral, and parallel. Granular per-branch locking lets agents work on many branches at once.
- Smart pull — analyzes changed files (manifest, Python fields, security XML, JS) and automatically decides whether to install, upgrade, restart, or do nothing.
- Auto-everything — auto branch creation, auto dependency install (
.oduflow/requirements.txt,apt_packages.txt), customodoo.conf, optional Traefik auto-HTTPS, stable port registry.
Beyond vibe coding: Spec-Driven Development
| Vibe Coding | Spec-Driven Development with Oduflow | |
|---|---|---|
| Input | Conversational prompts | Formal spec with acceptance criteria |
| Feedback | Human eyeballs the code | System returns errors, test results, and UI state automatically |
| Iteration | Human copy-pastes errors back | Agent retries autonomously via MCP |
| Scope | Single files, prototypes | Full modules against real databases |
| Verification | "Looks right" | Module installs, tests pass, UI works on production data |
Get started
pip3 install oduflow
or
uv tool install oduflow
Test run:
oduflow # stdio (local MCP clients)
oduflow --transport http # remote / multi-user (Streamable HTTP)
Add it to your MCP client config:
{
"mcpServers": {
"oduflow": { "command": "oduflow" }
}
}
Or on HTTP stransport:
{
"mcpServers": {
"oduflow": {
"url": "http://localhost:8000/mcp",
"type": "http"
}
}
}
Works with Claude, Cursor, Cline, Amp, and any MCP client. Supports any Odoo version. Every MCP tool is also one oduflow call away from your terminal and CI pipelines, and a built-in web dashboard + REST API give you a human window into the fleet.
Links & licensing
- Docs: https://docs.oduflow.dev
- Website: https://oduflow.dev
- GitHub: https://github.com/oduist/oduflow
Source-available under the Polyform Noncommercial License 1.0.0. Commercial use requires a license — see https://oduflow.dev.
Server Config
{
"mcpServers": {
"oduflow": {
"command": "npx",
"args": [
"mcp-remote",
"http://your.ip.address.or.domain:8000/mcp",
"--transport",
"http-only",
"--allow-http"
],
"env": {}
}
}
}Recommend Servers
View AllA Serper MCP Server
test