Python 3.10+ Docker MCP Business Source License 1.1 Odoo

Oduflow

An AI-first Odoo development and CI tool, powered by reusable database templates. Oduflow provisions isolated, ephemeral Odoo environments on Docker — one per git branch — and exposes them to AI coding agents via MCP, creating a closed feedback loop that enables fully autonomous Odoo development.

Beyond Vibe Coding: Spec-Driven Development

Vibe coding — chatting with an AI and eyeballing the output — was the first wave. It works for prototypes, but breaks down on real ERP systems where a module must install cleanly, pass tests, and work against production data.

Spec-Driven Development (SDD) is the next step: you write a precise specification of what the module should do, and the AI agent autonomously implements how — because it has a closed feedback loop with the running system:

┌──────────────────────────────────────────────────────┐
│                    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 MCP            │
┌──────▼──────────────────────────────┴────────────────┐
│               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             │
├──────────────────────────────────────────────────────┤
│            + Playwright MCP / other tools            │
│  • Navigate Odoo UI, click buttons, fill forms       │
│  • Verify business logic end-to-end                  │
│  • Validate acceptance criteria from the spec        │
└──────────────────────────────────────────────────────┘

The agent writes code, installs the module, reads the traceback, fixes the error, retries — and when it installs cleanly, it can open the browser via Playwright MCP to click through the UI, verify business flows, and validate acceptance criteria — all without human intervention. connect_as_user closes the last gap: it mints a passwordless Odoo session and hands back the cookie, so Playwright lands past /web/login as any role (admin, sales manager, portal) — no credentials to type, no login form.

	Vibe Coding	Spec-Driven Development
Input	Conversational prompts	Formal specification 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

Quick Start

1. Install

pip install oduflow

2. Start the MCP server

oduflow

That's it. On first launch, Oduflow automatically creates a default config and initializes shared infrastructure (Docker network, PostgreSQL, team directories).

The generated config is written to /etc/oduflow/oduflow.toml when writable, otherwise to ~/.oduflow/conf/oduflow.toml. Fresh configs include generated secrets for HTTP access: [team.1].auth_token for MCP clients and [team.1].ui_password for the Web Dashboard. The file is created with mode 0600; the secrets are never printed to the log, so read them from the config itself (sudo grep -E 'auth_token|ui_password' /etc/oduflow/oduflow.toml).

By default, the server starts in stdio mode (for local MCP clients). For remote/multi-user deployments:

oduflow --transport http
oduflow -t http

3. Connect an MCP client

stdio (local) — add to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "oduflow": {
      "command": "oduflow"
    }
  }
}

HTTP (remote) — point your MCP client to http://<host>:8000/mcp and send Authorization: Bearer <auth_token> using the token from oduflow.toml.

The bundled CLI can call that remote MCP server without a separate agent or MCP client configuration:

export ODUFLOW_MCP_URL="http://<host>:8000/mcp"
export ODUFLOW_MCP_TOKEN="<auth_token>"
oduflow client list_environments

The Web Dashboard is available at http://<host>:8000/. Sign in as admin with the ui_password from oduflow.toml; this is separate from the MCP Bearer token.

Documentation

For full documentation, visit oduflow.dev or see the docs/ folder:

Telemetry

Oduflow collects anonymous usage telemetry (first startup and environment creation events) to understand adoption. Only the event name, version, and a random instance ID are sent — no personal data or environment details. To opt out, add disable_telemetry = true to the [server] section of your oduflow.toml. See the documentation for details.

Licensing

Oduflow is source-available under the Business Source License 1.1. Evaluation, educational, and other non-commercial use is free forever. Commercial use requires a paid license in one of three tiers — Individual (solo developers), Business (internal company use), or Integrator (Odoo service providers) — visit oduflow.dev. Each release converts to the open-source MPL 2.0 four years after publication.

Metadata

Release files for oduflow 1.82.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for oduflow 1.82.0
File	Size	Uploaded	Provenance
oduflow-1.82.0.tar.gz	6.2 MB	Sep 23, 2026	With provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for oduflow 1.82.0
File	Interpreter	ABI	Platform	Reset
oduflow-1.82.0-py3-none-any.whl 957.6 kB Sep 23, 2026 With provenance	Python 3	none	any	Details

Total release size: 7.2 MB

Release files / oduflow-1.82.0.tar.gz

Download URL	oduflow-1.82.0.tar.gz
Size	6.2 MB
Tags	Source
SHA-256 checksum How to use checksums	`3c752d50f77de1e1eb5648bc10375e77a68fdf7c013f135057a19f842e6e3130`
BLAKE2b-256 checksum How to use checksums	`84830a8d3fa9828f5bafce5549c66710dd2a7ea167cb45b1f24b7e6f58038ced`
Upload date	Sep 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/oduflow/oduflow
Publishing commit: github.com/oduflow/oduflow/tree/a3c7238b3a77a3a944355420a23ca06d1658e3e3

Workflow

Publishing configuration: github.com/oduflow/oduflow/blob/a3c7238b3a77a3a944355420a23ca06d1658e3e3/.github/workflows/publish.yml
Publishing logs: github.com/oduflow/oduflow/actions/runs/35903702214/attempts/1

Artifact

Subject: oduflow-1.82.0.tar.gz
SHA-256 checksum: 3c752d50f77de1e1eb5648bc10375e77a68fdf7c013f135057a19f842e6e3130 Verifying attestations

Release files / oduflow-1.82.0-py3-none-any.whl

Download URL	oduflow-1.82.0-py3-none-any.whl
Size	957.6 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`4fd8a3acb2424b98b3d6d61eefc68a1cdf0940c342d04e3c937c84c49b73806c`
BLAKE2b-256 checksum How to use checksums	`faf8714136d61c2c3c1a0d9e0befb2d4647ab20022179b4a857db8ed64a5afca`
Upload date	Sep 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/oduflow/oduflow
Publishing commit: github.com/oduflow/oduflow/tree/a3c7238b3a77a3a944355420a23ca06d1658e3e3

Workflow

Publishing configuration: github.com/oduflow/oduflow/blob/a3c7238b3a77a3a944355420a23ca06d1658e3e3/.github/workflows/publish.yml
Publishing logs: github.com/oduflow/oduflow/actions/runs/35903702214/attempts/1

Artifact

Subject: oduflow-1.82.0-py3-none-any.whl
SHA-256 checksum: 4fd8a3acb2424b98b3d6d61eefc68a1cdf0940c342d04e3c937c84c49b73806c Verifying attestations

Security for oduflow 1.82.0

Report project as malware

Provenance

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Attestation for oduflow-1.82.0.tar.gz

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/oduflow/oduflow
Publishing commit: github.com/oduflow/oduflow/tree/a3c7238b3a77a3a944355420a23ca06d1658e3e3

Workflow

Publishing configuration: github.com/oduflow/oduflow/blob/a3c7238b3a77a3a944355420a23ca06d1658e3e3/.github/workflows/publish.yml
Publishing logs: github.com/oduflow/oduflow/actions/runs/35903702214/attempts/1

Artifact

Subject: oduflow-1.82.0.tar.gz
SHA-256 checksum: 3c752d50f77de1e1eb5648bc10375e77a68fdf7c013f135057a19f842e6e3130 Verifying attestations

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.