MCP-Odoo-Tools — CE, EE & online (Odoo 10-19)

A Claude Code / Cowork plugin that unifies Odoo tooling into one install:

• MCP server (primary) — a clean-room, MIT-licensed Python server exposing native Odoo tools (odoo_search, odoo_read, odoo_create, odoo_write, odoo_export_records_json/csv, odoo_version, ...) over JSON-RPC with automatic XML-RPC fallback, and a cross-version compatibility layer that makes a single tool call work across Community, Enterprise and online (SaaS) from Odoo 10 through 19.

• CLI fallback — a lightweight TypeScript XML-RPC CLI (Node-only) for when you can't run the MCP server, or for scripted batch access.

• Agents, skills, commands and domain context to drive both surfaces.

Built and maintained by Transgenia, a Registered partner of Anthropic. (Registered tier — this plugin is an independent open-source project, not an Anthropic-certified or first-party product.)

Why this exists

Odoo's model and field names drift across versions (account.invoice → account.move at v13, analytic fields at v16, package models near v19, API-key behavior on /jsonrpc at v17, and more), and Enterprise adds models Community lacks. This plugin absorbs those differences behind one stable tool surface so you don't hand-branch per version.

Related MCP server: odoo-mcp-server

Install

/plugin marketplace add Transgenia/MCP-Odoo-Tools-CE-EE-and-online
/plugin install odoo-tools
/odoo-tools:odoo-setup-mcp

The setup skill collects credentials (via environment) and verifies the connection with odoo_version.

Requirements

• MCP server: uv/uvx (ships its own Python), or Python 3.11+ to run python -m odoo_mcp from server/.

• CLI fallback (optional): Node.js 18+.

Configuration (environment)

* one of ODOO_API_KEY or ODOO_PASSWORD.

Credentials stay in your environment and the MCP server does not persist them to disk. Two caveats worth stating plainly:

• The optional CLI fallback writes a local .env with your credentials under ~/.claude/tools/odoo-cli. See SECURITY.md.

• When you drive Odoo through an AI agent, the tool results (the Odoo records you query) are returned to your MCP client and sent to your model provider (e.g. Anthropic, for Claude) to be processed, exactly like any other tool an agent uses. The MCP server talking directly to Odoo means Transgenia never proxies or stores your data; it does not mean company data is withheld from the model.

Telemetry (opt-in, disabled by default)

No data leaves your machine unless you opt in with ODOO_TELEMETRY=opt-in and manually share the payload shown by /odoo-doctor. When enabled, only plugin_version, odoo_version_major, edition/deployment labels and aggregate generic tool counters are included — never URL, DB, login, secrets, PII, modules or billing. No schedules, no boot hooks, no background sends. Details: SECURITY.md.

Support matrix

Details and the delta table: docs/compat-matrix.md.

Architecture

See docs/architecture.md. In short: transport (xmlrpc/jsonrpc/fallback) → session (auth + version/edition facts + schema cache) → compat (resolve model/field/capability) → tools → MCP stdio.

Scope

This is the public generic core: it talks to Odoo and nothing else. Any localization-, governance- or tenant-specific engines (e.g. country e-invoicing, approval workflows, backups, document AI) are intentionally out of scope and are not part of this repository.

Commercial support

Need help implementing this against your Odoo, or a custom AI/ERP integration? Transgenia offers AI and Odoo implementation services. Contact dev@transgenia.org. (This is the only Transgenia-specific content in the repo; the plugin itself is vendor-neutral and works with any Odoo instance.)

Development

cd server
uv venv && uv pip install -e ".[dev,cache]"   # or python -m venv + pip
pytest -q
ruff check src tests

License

MIT © Transgenia (Centrum Transgenia S.A.S. de C.V.). See LICENSE and NOTICE for third-party attributions.