Odoo

io.github.Helios-One-OyPublished by GitHub account Helios-One-Oyv0.1.0Updated Oct 29, 2026

Odoo orders, late lines, supplier promise dates, manufacturing and stock. Read-only by default.

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant read Odoo sales, purchasing, manufacturing and stock data, with one optional write tool for PO line promise dates.

What you can do
  • List open sales and purchase orders, including quotations and RFQs
  • Inspect a single order's lines, quantities and transfers, and find late sales or purchase lines with days late
  • Review supplier promise dates, manufacturing orders, work orders and shipments
  • Look up customers and suppliers by name, email, reference or VAT
  • Check product quantities on hand, forecast, incoming and outgoing
  • Optionally update one purchase order line's expected arrival date when writes are enabled
When to use it
Useful when an assistant should answer operational questions about an Odoo instance, such as which purchase lines are late, what the status of a sales order is, or what stock is available, without giving it broad ERP access.
Requirements
Runs locally over stdio via npx, so Node.js 20 or newer is needed. Requires an Odoo base URL (ODOO_URL), database name (ODOO_DB) and login (ODOO_USERNAME), plus either an Odoo API key (ODOO_API_KEY) or the user's password (ODOO_PASSWORD). The Odoo user must be allowed to use the external API, and the server needs network access to that Odoo instance.
Before you install
Stores Odoo credentials in the client configuration; an API key is recommended over ODOO_PASSWORD. The server acts with the configured user's Odoo access rights, so use a dedicated user with minimal rights. Writes are off unless ODOO_MCP_ENABLE_WRITES is true, and the write tool also needs an exact confirmation text per call; it changes a purchase order line's planned date. Only tested against self-hosted Odoo Community 17-19, not Odoo Online, Odoo.sh or Enterprise.

Installation

In SourceWeft

  1. Open Odoo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Odoo MCP server

An MCP server that lets an AI assistant (Claude Desktop, Claude Code, or any MCP client) read your Odoo sales, purchasing, manufacturing and stock data, and, only if you turn it on, update a purchase order line's promise date.

  • 12 read tools and 1 write tool (listed below).
  • Read-only by default. The write tool needs ODOO_MCP_ENABLE_WRITES=true on the server and an exact confirmation text on every call.
  • Talks to Odoo's external JSON-RPC API (/jsonrpc) as the user you configure. Odoo's access rights apply.
  • Runs locally over stdio. No telemetry; it connects only to your Odoo.

Built by Helios One. MIT license.

Quickstart (2 minutes)

You need Node.js 20 or newer and an Odoo user that can log in to the external API.

1. Get an API key in Odoo (recommended over a password): click your avatar, then My Profile / Preferences, open Account Security, click New API Key. Copy the key.

2. Add the server to your MCP client.

Claude Code:

sh
claude mcp add odoo \  -e ODOO_URL=https://odoo.example.com \  -e ODOO_DB=mydb \  -e [email protected] \  -e ODOO_API_KEY=your-api-key \  -- npx -y @heliosone/odoo-mcp

Claude Desktop: open Settings > Developer > Edit Config and add this to claude_desktop_config.json, then restart Claude Desktop:

json
{  "mcpServers": {    "odoo": {      "command": "npx",      "args": ["-y", "@heliosone/odoo-mcp"],      "env": {        "ODOO_URL": "https://odoo.example.com",        "ODOO_DB": "mydb",        "ODOO_USERNAME": "[email protected]",        "ODOO_API_KEY": "your-api-key"      }    }  }}

3. Ask, for example: "Which purchase order lines are late, and by how many days?" or "What is the status of S00042?"

Settings

VariableRequiredMeaning
ODOO_URLyesBase URL of your Odoo, e.g. https://odoo.example.com
ODOO_DByesDatabase name
ODOO_USERNAMEyesThe user's login
ODOO_API_KEYone of these twoAPI key of that user (used in place of the password)
ODOO_PASSWORDThe user's password
ODOO_MCP_ENABLE_WRITESnotrue allows the write tool. Anything else keeps the server read-only.
ODOO_TIMEOUT_MSnoRequest timeout, default 30000

The server starts even when settings are missing, so your client can list the tools. Each call then returns CONFIGURATION_ERROR with the names of the missing settings.

Tools

ToolWhat it returns
list_open_sales_ordersConfirmed sales orders not fully delivered (includeQuotations adds quotations)
list_open_purchase_ordersConfirmed purchase orders not fully received (includeRfqs adds RFQs)
get_order_statusOne sales or purchase order with lines (ordered / delivered or received / invoiced) and its transfers. By id, number or customer/vendor reference.
list_supplier_promise_datesOpen lines on confirmed POs with the vendor's expected arrival date, soonest first
list_late_purchase_linesPO lines past their expected arrival and not fully received, with days_late
list_late_sales_linesSales lines past their promised date and not fully delivered, with days_late. Promised date = the order's commitment date, else order date + the line's lead time.
list_manufacturing_ordersManufacturing orders with state, quantity, planned dates, component availability
list_work_ordersWork orders: operation, work center, state, expected and actual duration
list_shipmentsReceipts, deliveries or internal transfers; lateOnly for those past their scheduled date
lookup_customerContacts by name, email, reference or VAT, customers first
lookup_supplierContacts by name, email, reference or VAT, suppliers first
get_inventory_on_handProduct quantities: on hand, forecast, incoming, outgoing
update_po_line_promise_dateWrite. Sets one PO line's expected arrival date. See below.

List tools take limit (default 50, max 500) and offset. Results are Odoo's own field values, plus a few computed fields (qty_open, days_late, promised_date). Fields that do not exist in your Odoo version are left out.

The write tool

update_po_line_promise_date changes date_planned on one purchase order line (for example after a vendor confirms a new date). It runs only when both are true:

  1. the server was started with ODOO_MCP_ENABLE_WRITES=true, and
  2. the call includes "confirmation": "CONFIRM update_po_line_promise_date".

Otherwise it returns WRITES_DISABLED or CONFIRMATION_REQUIRED and does not call Odoo. A date without a time is stored as 12:00 UTC so it shows as the same day in most time zones. The result shows the value before and after.

What has been tested

Tested on 24 October 2026, with the packed npm tarball installed into an empty project and its odoo-mcp command driven over stdio by the official MCP TypeScript SDK client, against fresh self-hosted Odoo Community 17.0, 18.0 and 19.0 (built from the official odoo/odoo branches; Sales, Purchase, Inventory and Manufacturing installed; fictional records). In each version:

  • all 13 tools were listed and all 12 read tools returned the seeded records (21 tool calls and 25 checks per version, all passed);
  • the write tool was refused with writes off (WRITES_DISABLED), refused without the confirmation text (CONFIRMATION_REQUIRED), then succeeded, and a direct Odoo read confirmed the new date;
  • the server logged in with an Odoo API key; one session used the plain password instead, and a wrong password returned AUTH_FAILED;
  • one call also went through the MCP Inspector CLI.

Logs: proof/. Unit tests (npm test, against an in-memory fake Odoo) pass on Node.js 20 and 25.

Not tested: Odoo Online (odoo.com hosting) and Odoo.sh, Odoo Enterprise, Odoo versions before 17, multi-company setups, and large databases. Odoo Online offers the external API only on some plans. Odoo 19 deprecated /jsonrpc (removal planned for Odoo 22, fall 2028, and Odoo Online 21.1, winter 2027) in favour of its JSON-2 API; this server does not use JSON-2 yet. Odoo 19 logs a deprecation warning for each /jsonrpc call.

Development

sh
npm cinpm test

proof/run-live.sh 18.0 repeats the live test in a disposable Linux machine (it installs PostgreSQL and Odoo; do not run it on your workstation).

Security

See SECURITY.md. Use a dedicated Odoo user with only the rights the assistant needs.

License

MIT, see LICENSE.

Source: README.md at commit f12961c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts