Odoo MCP

Odoo MCP runs locally from a Python package published to PyPI: odoo-erp-mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx odoo-erp-mcp. It reads these environment variables: ODOO_MCP_ODOO_URL (required), ODOO_MCP_ODOO_DATABASE (required), ODOO_MCP_ODOO_USERNAME (required), ODOO_MCP_ODOO_API_KEY (required, secret), ODOO_MCP_ALLOWED_COMPANY_IDS (required) and ODOO_MCP_DEFAULT_COMPANY_ID (required); set them in the client's configuration for this server. Required arguments: --config.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "odoo-mcp": {
      "command": "uvx",
      "args": [
        "odoo-erp-mcp"
      ],
      "env": {
        "ODOO_MCP_ODOO_URL": "<value>",
        "ODOO_MCP_ODOO_DATABASE": "<value>",
        "ODOO_MCP_ODOO_USERNAME": "<value>",
        "ODOO_MCP_ODOO_API_KEY": "<secret>",
        "ODOO_MCP_ALLOWED_COMPANY_IDS": "<value>",
        "ODOO_MCP_DEFAULT_COMPANY_ID": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect