mcp-server-odoo MCP — Use Cases, Install & Live Demo

Why use it

Key features

Works with Odoo 16+ (standard mode needs the MCP Odoo module) or any version in YOLO mode
Smart field selection — default 15 most relevant fields per model, no noise
Read-only mode via ODOO_YOLO=read — safe for connecting to production
API key auth (preferred) or username/password
Locale support via ODOO_LOCALE for multilingual Odoo instances

Live Demo

What it looks like in practice

server-odoo.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "server-odoo",
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "server-odoo": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-server-odoo"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add server-odoo -- uvx mcp-server-odoo

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use mcp-server-odoo

Answer ad-hoc sales questions against Odoo

👤 Ops managers, founders using Odoo as their source of truth ⏱ ~10 min beginner

When to use: 'What were last week's top 5 customers by revenue?' — without writing XML-RPC.

Prerequisites

Odoo API key — Odoo: user profile > Preferences > API Keys > New
ODOO_URL, ODOO_DB, ODOO_API_KEY env vars — Set in your MCP client config

Flow

List available models

list_models — which Odoo models can we query in this instance?✓ Copied

→ Model catalog with descriptions
Run the query

In sale.order, find orders with date_order between last Monday and today, group by partner_id, sum amount_total, top 5.✓ Copied

→ Ranked customer list with totals
Drill in

For the top customer, show the last 3 orders with their line items.✓ Copied

→ Detailed breakdown

Outcome: A business answer from ERP data without leaving chat.

Pitfalls

Multi-currency totals aren't converted — Specify currency_id in the filter, or convert in the LLM layer
ODOO_YOLO=true is dangerous in prod — Use ODOO_YOLO=read or leave unset; enable full access only in a staging DB

Combine with: notion

Clean up stale CRM leads in Odoo

👤 Sales ops ⏱ ~30 min intermediate

When to use: Leads pile up with no activity; you want to reassign or archive.

Flow

Find stale leads

In crm.lead, find leads where stage_id is not 'Won' and last activity > 60 days ago.✓ Copied

→ Stale lead list
Propose actions

Classify each: archive, reassign to team lead, or ping current owner.✓ Copied

→ Classification per lead
Apply in batches (read-only first!)

Dry run only: show what would change if I archived the 'archive' bucket.✓ Copied

→ Dry-run summary; then confirm before update_record

Outcome: A cleaner pipeline with auditable changes.

Pitfalls

Archiving leads other teams depend on — Always dry-run first; tag archived leads rather than delete

Draft follow-ups for unpaid invoices

👤 AR and finance ⏱ ~25 min intermediate

When to use: Monthly dunning run.

Flow

Pull overdue invoices

In account.move, find invoices where state='posted', payment_state='not_paid', invoice_date_due < today - 15.✓ Copied

→ Overdue list with partner + amount
Draft a polite follow-up per customer

For each, draft an email in the customer's preferred language using ODOO_LOCALE settings.✓ Copied

→ Per-invoice draft text

Outcome: Dunning emails ready to send (human still reviews).

Combinations

Pair with other MCPs for X10 leverage

server-odoo + notion

Pull a sales snapshot from Odoo, post to Notion for stakeholders

Run last-month sales by product category from Odoo, post as a Notion table under Finance / Monthly.✓ Copied

server-odoo + postgres

Cross-reference Odoo data with a warehouse replica for heavy analytics

For top-10 Odoo customers, pull their web-session counts from the Postgres analytics DB.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
list_models	(none)	First-run discovery	1 XML-RPC call
search_records	model: str, domain?: filter, fields?: str[], limit?: int	Any read query	1 XML-RPC call
get_record	model, id	Known id, need full detail	1 call
create_record	model, values: object	Only with ODOO_YOLO=true or API key granting write	1 call (write)
update_record	model, id, values	Writes — confirm first	1 call (write)
delete_record	model, id	Rarely — archive is usually better	1 call (write, destructive)
list_resource_templates	(none)	Explore available resource URIs	free

Cost & Limits

What this costs to run

API quota: Bounded by Odoo server; no per-call cost
Tokens per call: Smart-field responses keep responses under 1k tokens per record
Monetary: Free; you need an Odoo instance (community or enterprise)
Tip: Always pass explicit fields= on big models like product.template to avoid pulling 200 fields.

Security

Permissions, secrets, blast radius

Minimum scopes: API key or user with read rights on the models you query

Credential storage: ODOO_API_KEY in env var; never commit to repo

Data egress: Calls to your Odoo instance only

Never grant: ODOO_YOLO=true in production

XML-RPC is cleartext unless ODOO_URL uses https — always use https in prod.
User/password auth is supported but prefer API keys.

Troubleshooting

Common errors and fixes

Access Denied on model

API key user doesn't have access rights for that model. Grant or switch user.

Verify: Odoo: Settings > Users > Access Rights

Database not found

Set ODOO_DB explicitly; auto-detection fails when db listing is disabled.

Verify: curl -d '{"jsonrpc":"2.0","method":"call","params":{"service":"db","method":"list"}}' $ODOO_URL/jsonrpc

MCP Odoo module not installed

In standard mode, install the mcp_odoo community module, or switch to ODOO_YOLO=read mode.

Verify: Odoo: Apps > search mcp_odoo

Alternatives

mcp-server-odoo vs others

Alternative	When to use it instead	Tradeoff
Direct XML-RPC via fetch MCP	You only need one specific query	No smart field selection; boilerplate-heavy
postgres MCP on Odoo's DB	You want raw SQL and can connect to the underlying Postgres	Bypasses Odoo ACLs — dangerous without care

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills