Skip to content

Commercial support

MCP-Odoo-Tools is an open-source (MIT) project: you can install it, configure it and operate it on your own following this manual.

Start here

In Claude Code, run /odoo-tools:odoo-setup-mcp: the guided route for setup, verification, hands-on training, daily use and deployment. No Odoo to practice with? /odoo-tools:deploy-local starts a local sandbox. /odoo-doctor checks an existing connection.

Using Cowork or Claude chat?

The Odoo tools do not run there: the plugin's skills and commands load, but those apps do not start its MCP server and have no form for the connection options. Nothing is wrong with your account, your Odoo or your Python. If Claude or the app shows this plugin's server as not_started with the reason user_config_unsupported, that is this case, not a bug, and no update changes it. Open a local session of the Code tab of Claude Desktop (or Claude Code in a terminal, VS Code or JetBrains): the plugin you installed on your Claude account appears there as a synced plugin when you sign in with the same account. A cloud session of the Code tab does not work either, for another reason: your connection options stay on your computer. Or ask Transgenia for assisted setup (below). See Where it works.

If something fails: the support report

Run /odoo-tools:odoo-doctor. It first checks whether the Odoo tools run where you are, then the connection (in Claude Code, also which odoo-tools copy answers and whether there is a second copy or one older than 1.5.0; see Two copies of odoo-tools), and it ends with a support report you can send to Transgenia. The report holds no API keys, passwords, URLs, logins or record data.

  • In Claude Code the doctor builds it with python3 <plugin folder>/server/run_stdio.py --diagnose, which only reads the plugin's local diagnostics and audit files and contacts nothing.
  • In Cowork, Claude's commands run in a virtual machine, not on your computer, so the doctor writes the report from the line the plugin's session-start hook leaves for Claude (Cowork runs the plugin's hooks on your computer itself): the surface, the app that started the session, the MCP server's last status and the folder of the diagnostics files.
  • In Claude chat the plugin's hooks do not run, so the report names the surface only.
  • In Cowork, Claude chat or a cloud session, if the app showed a status and a reason for this plugin's server (such as not_started and user_config_unsupported), the doctor adds them to the report as they are, with the app's version: they confirm the surface, they are not a fault to fix.

In Claude Code the report looks like this (trimmed). It holds the versions, the diagnostics folder (your home folder shows as ~), the last server and hook events re-checked against the allowlist, the audit counts of the last 7 days by status and refusal rule, the policy the server loaded at its last start, and the policy computed offline from the command's own environment (which lacks the plugin's options, so it is labelled as such):

odoo-tools support report (no keys, URLs, logins or record data)
plugin: 1.6.0
python: 3.12.4
os: Darwin 24.6.0 arm64
diagnostics folder: ~/.claude/plugins/data/<plugin id>/diagnostics (exists)
last 5 server events (server.jsonl):
  {"v":1,"ts":"2026-10-30T15:02:11Z","event":"start","pid":4242,"plugin":"1.6.0",...,"settings":{"url":true,"db":true,"login":true},"credential":"api_key","audit":"file","entrypoint":"cli"}
  {"v":1,"ts":"2026-10-30T15:02:14Z","event":"connect","pid":4242,"ok":true,"transport":"json2","odoo_major":19,"edition":"enterprise","deployment":"saas"}
last 3 hook events (hook.jsonl):
  {"v":1,"ts":"2026-10-30T15:02:10Z","event":"session_start","source":"startup",...,"entrypoint":"cli","server_last":"ok","age_h":20,"container":false}
audit, last 7 days: 2 files, 41 calls; by status: ok 39, refused 2; refusals by rule: profile:standard 2
policy at the server's last start: profile standard, digest 21524d1933f3, locked no
policy computed offline from this command's environment (the plugin's options may differ; never contacts Odoo): profile standard, digest 21524d1933f3, locked no, policy file no, read-only no

The files behind it stay on your computer, in the diagnostics folder of the plugin's data folder. In Claude Code that is ~/.claude/plugins/data/<plugin id>/diagnostics/ (on Windows, %USERPROFILE%\.claude\plugins\data\<plugin id>\diagnostics\); in Cowork the doctor tells you the folder, as the session-start hook reported it. The files hold metadata only (what started, which surface, which kind of error), never values, and the plugin never sends them anywhere. Attach them to your email if support asks. See Privacy.

Transgenia services

If you prefer guidance, Transgenia offers implementation services for AI and Odoo:

  • Diagnosis of your instance (version, edition, modules, flows that are candidates for AI automation).
  • Connection and read-only pilot before touching production data.
  • Write governance (human review before creating/modifying records).
  • Custom integrations between Odoo, AI agents and your systems.
  • Maintenance and support of the plugin and your Odoo connection.
  • Training for your team by role (sales, accounting, inventory, management).
  • Assisted deployment to production: hosting, security, migrations between Odoo versions and roll-out to several users.

Transgenia is a registered partner of Anthropic (Registered tier) and operates governed AI agents in its own production. We work with verifiable implementations in the healthcare and B2B sectors.

Contact

Official channels

Contact Transgenia only through these channels:

Transgenia will never ask for your Odoo API key or password by chat or email.

Where the plugin suggests it

Since v1.3.0 the plugin mentions these channels at the moments they help, not in every answer:

  • when the Odoo tools do not run where you are (Cowork or Claude chat): the session-start hook and /odoo-tools:odoo-doctor offer a local session of the Code tab of Claude Desktop and, after it, assisted setup by Transgenia;
  • when setup is blocked (credential, authentication or transport errors, and /odoo-doctor when something fails);
  • at the end of the training in the guided route;
  • at the end of the local sandbox and of the deployment phase;
  • when you ask for maintenance, support, training, customization or deployment help.

Bugs and feature requests

Open an issue in the repository with the plugin version, the Odoo version and edition, and the support report of /odoo-tools:odoo-doctor (it contains no credentials). For security vulnerabilities, follow Security.

Project resources

Brand honesty

Transgenia is a registered partner of Anthropic. This plugin is an independent open-source project; it is neither a certified nor a first-party product of Anthropic. It is listed in Anthropic's plugin directory, where each new version arrives once an Anthropic reviewer approves it, so the directory may offer an earlier version than the one this manual describes.