Odoo MCP Pro

What Odoo MCP Pro MCP server does

Odoo MCP Pro MCP server gives MCP-compatible AI clients an interface to Odoo business data. An assistant can search records with filters, retrieve a record by ID, inspect available models, and ask for server and connection information. It can also create, modify, delete, or import records, including bulk operations.

The connector is model-agnostic. The README lists examples across contacts, quotations, sales orders, invoices, inventory, CRM, and HR, while noting that any Odoo model can be used. Odoo remains responsible for permissions, record rules, and business logic, so the API key's access determines which operations are allowed.

How it works

The Odoo MCP Pro MCP server implements the Model Context Protocol and exposes callable tools that an AI assistant selects in response to a request. Available operations include search_records, get_record, list_models, list_resource_templates, server_info, and singular or plural create, update, and delete tools. import_records supports idempotent upserts using external IDs, matching Odoo CSV-import behavior.

For Odoo 19 and later, the connector uses the JSON/2 API. For Odoo 14 through 18, it uses XML-RPC. Version detection and protocol selection happen automatically, so no separate API transport setting is required for the supported Odoo versions.

Setup and configuration

Self-hosting requires Python 3.10 or newer and an Odoo URL plus API key. Install the package from the Git repository with pip, then run the module in stdio mode for local clients such as Claude Desktop or Claude Code:

ODOO_URL=https://mycompany.odoo.com ODOO_API_KEY=your_key python -m mcp_server_odoo

The same module can run with streamable HTTP by supplying --transport streamable-http, a host, and a port. HTTP mode has no built-in authentication; place it behind a reverse proxy or restrict access at the network level. A Claude Desktop configuration can provide ODOO_URL and ODOO_API_KEY in the server's env object.

A hosted deployment is also documented. It accepts an Odoo URL and API key through the provider's setup flow and supports managed OAuth 2.1. The hosted and self-hosted options differ: self-hosting is single-tenant and configured with environment variables, while the hosted offering provides per-user connections and an administrative interface.

Tools and capabilities

• Search any Odoo model with domain filters, sorting, and pagination.
• Fetch individual records with smart field selection.
• Discover Odoo models and resource URI templates.
• Create, update, and delete one or multiple records.
• Import records through external-ID-based upserts.
• Check server version and connection status.

Limitations and notes

Self-hosted HTTP mode should not be exposed directly because it has no built-in authentication. A local stdio installation runs on the machine where it is installed, while the hosted option can be used from supported remote clients.

The server is described as a stateless proxy that does not store or cache business data. In the hosted version, API keys are encrypted at rest with AES-128/Fernet; Odoo API keys still govern access, and revoking a key in Odoo cuts off that access. Multi-tenant connections, per-user configuration, OAuth, and an admin UI belong to the separate hosted commercial offering rather than the self-hosted open-core server.

Odoo MCP Pro MCP server supports Odoo 14–20. An access-denied result generally indicates that the configured Odoo API key lacks the required model permissions or record access.