Odoo MCP Server

Odoo MCP server exists for a simple reason — assistants are far more useful when they can act on Odoo directly instead of describing what you should do. An AI business analyst for Odoo ERP — one-call reports with verdicts, over MCP.

What you get

Each tool answers a whole management question in a single call, returning a structured report with a verdict — not a raw dump you have to interpret.

Setting it up

The server ships on PyPI as odoo-pulse, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Odoo is connected, these are the calls the assistant has available:

• pipeline_review — CRM funnel by stage, stalled deals, weighted revenue, recent win rate
• sales_snapshot — Revenue this period vs last (Δ%), top customers/products, stale quotations
• receivables_health — AR/AP aging buckets, % overdue, top debtors
• inventory_risk — Shortages (negative forecast) and dead stock
• absence_overview — Who's off this week, pending approvals, thin-coverage departments
• procurement_watch — Purchasing: late receipts, stale RFQs, open spend per vendor
• production_health — Manufacturing: orders behind their planned start, stuck WIP
• project_profitability — Projects: hours logged vs allocated, cost/revenue/margin, budget burn verdict
• project_budget — Budget vs actual per project, line by line — over-plan lines and spend the budget doesn't capture

Configuration and credentials

You will need 2 environment variables: ODOO_URL, ODOO_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Odoo.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the odoo mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Odoo's toolset — pipeline_review, sales_snapshot, receivables_health and 6 more — is a fair guide to whether it matches your workflow. It is maintained by minhhq-a1; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Odoo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.