MCP Server Odoo

What ivnvxd/mcp-server-odoo does

ivnvxd/mcp-server-odoo gives an MCP client access to an Odoo instance through tools for reading and changing business records. It can search any model enabled for MCP access, retrieve records by ID, inspect model fields, and list available models. CRUD operations cover creating, updating, and deleting records, subject to Odoo permissions and the server's security configuration.

The server also supports operational tasks beyond basic record access. Agents can post notes or comments to a record's chatter, request server-side totals and groupings, and retrieve binary or attachment resources through resource URIs. A session context exposes the connected user, timezone, active company, other permitted companies, and guidance for handling UTC datetimes.

How it works

The MCP process runs on the computer hosting the client, rather than on the Odoo server. It connects to Odoo using the configured URL and either an API key or username and password. MCP clients communicate with the process over the standard local process configuration, or the server can be started with streamable HTTP.

For production use, the documented standard mode targets Odoo 16.0 or later with the Odoo MCP module installed. YOLO mode can connect to any Odoo version with XML-RPC enabled, but it bypasses MCP security and is intended for development, testing, and demonstrations. The optional call_model_method tool is more restricted: it is available only when both YOLO mode is fully enabled and method calls are explicitly enabled.

Setup and configuration

Install Python 3.10 or later and UV, then configure the server with uvx mcp-server-odoo. Pip, pipx, source installation, and Docker are also documented. The minimum connection setting is ODOO_URL. Authentication requires either ODOO_API_KEY or both ODOO_USER and ODOO_PASSWORD. ODOO_DB is optional because the database can be detected when it is not supplied.

ODOO_LOCALE selects the language used for Odoo responses. ODOO_YOLO controls the development mode, with supported values described as off, read, or true. ODOO_MCP_ENABLE_METHOD_CALLS enables the workflow-method escape hatch only alongside ODOO_YOLO=true.

The README includes configuration examples for Claude Desktop, Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf, and Zed. Docker can run the server over stdio or streamable HTTP. HTTP transport has no built-in authentication, so its port should be limited to trusted networks or protected by an authenticating reverse proxy.

Tools and capabilities

The ivnvxd/mcp-server-odoo tool set includes:

• search_records for filtered searches across Odoo models.
• get_record for reading a record by ID.
• get_fields for discovering field types, labels, required and readonly status, relations, and selection values.
• get_current_context, list_models, and list_resource_templates for session and server discovery.
• create_record, update_record, and delete_record for record changes.
• post_message for adding internal notes or follower-facing comments to chatter.
• aggregate_records for counts, sums, and groupings performed server-side instead of returning raw rows.
• call_model_method for public business methods such as confirming a sale order or posting an invoice, when its opt-in security requirements are met.

The server also provides pagination for larger result sets, model-aware field selection, hierarchical text output, multilingual responses, and resource access for images, documents, and ir.attachment files.

Limitations and notes

Permissions remain important: normal operations use Odoo access controls, while YOLO mode intentionally reduces MCP-side protections. The method-call tool can invoke public business methods and should be enabled only when that behavior is acceptable. HTTP deployments require external access control because the transport itself does not authenticate callers.

Before changing records or invoking workflow methods, agents should inspect the model schema and session context so they use the correct fields, company, user, and datetime interpretation.