Name: Odoo
Author: Helios-One-Oy

Odoo MCP

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

Grade A Local · stdio API key 13 tools v0.1.0 MIT

No reviews yet by Helios-One-Oynpm 361 Runs on your machine, nothing hosted

99/100

trust score

downloads a day

local

runs on your machine

361

downloads in 30d

What it does

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

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'ODOO_URL=${ODOO_URL}' --env 'ODOO_DB=${ODOO_DB}' --env 'ODOO_USERNAME=${ODOO_USERNAME}' --transport stdio helios-one-oy-odoo-mcp '--' npx -y @heliosone/odoo-mcp

# 2 — ask your agent for something these tools do
#   list_open_sales_orders, list_open_purchase_orders, get_order_status and 10 more

It needs ODOO_URL, ODOO_DB, ODOO_USERNAME: this reads them from your environment, so export them first.

Odoo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

Helios-One-Oy1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Odoo as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads ODOO_URL (Odoo base URL, e.g. https://odoo.example.com), ODOO_DB (Odoo database name), ODOO_USERNAME (Odoo login (user email)) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx ODOO_URL …, setx ODOO_DB …, setx ODOO_USERNAME … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'ODOO_URL=${ODOO_URL}' --env 'ODOO_DB=${ODOO_DB}' --env 'ODOO_USERNAME=${ODOO_USERNAME}' --transport stdio helios-one-oy-odoo-mcp '--' npx -y @heliosone/odoo-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: ODOO_URL — Odoo base URL, e.g. https://odoo.example.com; ODOO_DB — Odoo database name; ODOO_USERNAME — Odoo login (user email). You set them in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Confirmed Odoo sales orders (state "sale") that are not fully delivered (delivery_status is not "full", where the field exists). includeQuotations adds draft and sent quotations. Newest first.

Parameter	Type	Required	Notes
query	string	no	Match order number, customer name or customer reference.
includeQuotations	boolean	no	—
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Confirmed Odoo purchase orders (state "purchase" or locked "done") that are not fully received (receipt_status is not "full", where the field exists). includeRfqs adds draft, sent and to-approve RFQs. Newest first.

Parameter	Type	Required	Notes
query	string	no	Match PO number, vendor name or vendor reference.
includeRfqs	boolean	no	—
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

One sales or purchase order with its lines (ordered, delivered/received and invoiced quantities) and its transfers (receipts or deliveries). Find it by Odoo id or by order number / customer or vendor reference.

Parameter	Type	Required	Notes
orderType	string	no	—
orderId	integer	no	Odoo record id.
name	string	no	Order number such as S00012 or P00007, or the customer/vendor reference.

Purchase order lines on confirmed POs with the vendor's expected arrival date (date_planned), soonest first. By default only lines with quantity still to receive.

Parameter	Type	Required	Notes
supplier	string	no	Match vendor name.
includeReceived	boolean	no	—
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Lines on confirmed POs whose expected arrival (date_planned) is before asOf and that are not fully received. Adds qty_open and days_late.

Parameter	Type	Required	Notes
asOf	string	no	Cut-off date YYYY-MM-DD (default: today, UTC).
supplier	string	no	Match vendor name.
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Lines on confirmed sales orders that are not fully delivered and whose promised date is before asOf. Promised date = the order's commitment_date if set, otherwise order date + the line's customer lead time (as Odoo computes it). Adds promised_date, qty_open and days_late.

Parameter	Type	Required	Notes
asOf	string	no	Cut-off date YYYY-MM-DD (default: today, UTC).
customer	string	no	Match customer name.
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Odoo manufacturing orders (mrp.production) with state, quantity, planned start/finish and component availability. By default excludes done and cancelled orders. Needs the Manufacturing app.

Parameter	Type	Required	Notes
query	string	no	Match MO number, product or source document.
includeDone	boolean	no	—
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Odoo work orders (mrp.workorder): operation, work center, state, expected and actual duration. Optionally for one manufacturing order. By default excludes done and cancelled. Needs the Manufacturing app with work orders.

Parameter	Type	Required	Notes
manufacturingOrderId	integer	no	—
includeDone	boolean	no	—
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Odoo transfers (stock.picking): receipts (incoming), deliveries (outgoing) or internal moves, with scheduled and done dates. By default only transfers not done or cancelled. lateOnly keeps those scheduled before asOf.

Parameter	Type	Required	Notes
direction	string	no	—
includeDone	boolean	no	—
lateOnly	boolean	no	—
asOf	string	no	Cut-off date YYYY-MM-DD (default: today, UTC).
query	string	no	Match transfer number, source document or partner name.
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Find contacts (res.partner) by name, email, reference or VAT number. Contacts with more sales (customer_rank) come first.

Parameter	Type	Required	Notes
query	string	yes	Name, email, internal reference or VAT number (partial match).
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Find contacts (res.partner) by name, email, reference or VAT number. Contacts with more purchases (supplier_rank) come first.

Parameter	Type	Required	Notes
query	string	yes	Name, email, internal reference or VAT number (partial match).
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

Product quantities from Odoo (product.product): on hand (qty_available), forecasted (virtual_available), incoming and outgoing, across all warehouses.

Parameter	Type	Required	Notes
query	string	no	Match product name or internal reference (SKU).
productId	integer	no	—
limit	integer	no	Maximum rows to return (1-500, default 50).
offset	integer	no	Rows to skip, for paging (default 0).

WRITE. Sets the expected arrival date (date_planned) of one purchase order line, e.g. after a vendor confirms a new date. Refused unless the server was started with ODOO_MCP_ENABLE_WRITES=true AND confirmation is exactly "CONFIRM update_po_line_promise_date". A date without a time is stored as…

Parameter	Type	Required	Notes
lineId	integer	yes	purchase.order.line id (see list_supplier_promise_dates).
promiseDate	string	yes	—
confirmation	string	no	Must be exactly "CONFIRM update_po_line_promise_date".

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Odoo or to call it, at any volume.

ATrust score 99 / 100

Release 0.1.0 · scanned 28 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score99

Findings0 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationrepo

Surface digest0bac7461fda394015bae775651981c0819e0e6ad91b9cb26f4084e649d71d425

Score vectorthreat 100 → client 99

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfacenot available

Implementation sourceread

Package metadataread

Live transportnot available

No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
No per-tool rows for this release — see the note below.

No tool surface was enumerated, so there is nothing to attribute a capability to.

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest0bac7461fda39401

Scanned2026-10-28

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.