Odoo MCP Server
Integrates with Odoo's external JSON-RPC API to read sales, purchasing, manufacturing, and stock data. Provides tools for open sales and purchase orders, order status, supplier promise dates, late purchase and sales lines, manufacturing and work orders, shipments, customer/supplier lookup, and inventory on hand. Optionally supports a guarded write operation to update a purchase order line's promise date.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Odoo MCP ServerWhich purchase order lines are late, and by how many days?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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=trueon 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:
claude mcp add odoo \
-e ODOO_URL=https://odoo.example.com \
-e ODOO_DB=mydb \
-e ODOO_USERNAME=me@example.com \
-e ODOO_API_KEY=your-api-key \
-- npx -y @heliosone/odoo-mcpClaude Desktop: open Settings > Developer > Edit Config and add this to claude_desktop_config.json, then restart Claude Desktop:
{
"mcpServers": {
"odoo": {
"command": "npx",
"args": ["-y", "@heliosone/odoo-mcp"],
"env": {
"ODOO_URL": "https://odoo.example.com",
"ODOO_DB": "mydb",
"ODOO_USERNAME": "me@example.com",
"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?"
Related MCP server: MCP Server for Odoo
Settings
Variable | Required | Meaning |
| yes | Base URL of your Odoo, e.g. |
| yes | Database name |
| yes | The user's login |
| one of these two | API key of that user (used in place of the password) |
| The user's password | |
| no |
|
| no | Request 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
Tool | What it returns |
| Confirmed sales orders not fully delivered ( |
| Confirmed purchase orders not fully received ( |
| One sales or purchase order with lines (ordered / delivered or received / invoiced) and its transfers. By id, number or customer/vendor reference. |
| Open lines on confirmed POs with the vendor's expected arrival date, soonest first |
| PO lines past their expected arrival and not fully received, with |
| Sales lines past their promised date and not fully delivered, with |
| Manufacturing orders with state, quantity, planned dates, component availability |
| Work orders: operation, work center, state, expected and actual duration |
| Receipts, deliveries or internal transfers; |
| Contacts by name, email, reference or VAT, customers first |
| Contacts by name, email, reference or VAT, suppliers first |
| Product quantities: on hand, forecast, incoming, outgoing |
| Write. 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:
the server was started with
ODOO_MCP_ENABLE_WRITES=true, andthe 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
npm ci
npm testproof/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.
This server cannot be deployed
Maintenance
Related MCP Connectors
Connect AI to Odoo ERP 14-20: search, create, update and manage records in natural language.
Connect your Odoo to Claude and ChatGPT: ask about sales, stock, customers and invoices.
1Read, write and run Odoo actions from any AI app, as each user, with approval rules per colleague.
Odoo MCP connector for Claude & ChatGPT: ask sales, invoices, stock in plain words. Read-only.
51
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Odoo ERP systems through natural language to search records, create entries, update data, and manage business operations. Supports secure authentication and configurable access controls for production environments.Mozilla Public 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Odoo ERP systems through natural language, allowing users to search, create, update, and manage business records like customers, products, and invoices across any Odoo instance.29 PyPI1Mozilla Public 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to interact with Odoo ERP as the authenticated user, with tools for discovery, planning, and mutations bounded by user permissions.3623 npm2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Odoo ERP via the external API. It supports listing models, describing schemas, searching, aggregating, creating, updating, deleting records, and invoking business methods, with a configurable permission matrix for safety.-