Installation and Requirements

The MCP server is an Odoo application module. Install it in the same Odoo 19 environment that owns the data; do not deploy it as an unrelated external service.

Warning: Test on staging first The package includes static validation, but installation, OAuth browser flow, client discovery, scheduled jobs, and live ORM behavior must be tested on an Odoo 19 staging database before production.

Requirements

• Odoo 19 with permission to install applications and restart the Odoo service.
• An internal Odoo administrator for initial configuration.
• A stable public HTTPS origin for hosted AI clients, for example https://odoo.example.com.
• A reverse proxy that forwards the /mcp and OAuth routes to Odoo without rewriting the public host or protocol.
• Correct Odoo database routing. In multi-database environments, the public hostname must resolve to the intended database.
• A current database backup before installation or upgrade.

Install from a module ZIP or addons directory

1. Back up the Odoo database and the current custom-addons directory.
2. Place the niyu_mcp_server directory in an Odoo addons path. The module directory itself must contain manifest.py.
3. Ensure the Odoo service account can read the module files.
4. Restart Odoo so the new Python code is loaded.
5. Open Apps, update the Apps list, search for Niyu MCP Server, and install it.
6. For a command-line upgrade, update the module with -u niyu_mcp_server against the intended database, then restart normally.

Dependencies

The Odoo module depends on base, mail, and base_import_module. The optional shared Redis backend requires the Python redis package and a reachable Redis service. The optional local bridge requires a separate Python environment with mcp and httpx.

Reverse-proxy checklist

• Serve the public origin over HTTPS with a valid certificate.
• Forward Host and X-Forwarded-Proto correctly.
• Do not redirect /mcp to an HTML login page.
• Allow POST, GET, OPTIONS, and DELETE requests to /mcp.
• Do not cache MCP, OAuth, health, guide, documentation, or dashboard responses at the proxy.

Installation validation

1. Open Settings and confirm the MCP Server application block exists.
2. Open the MCP Server app and confirm Connections, Access Bundles, API Keys, Async Jobs, Dashboards, Prompt Templates, Audit Logs, and Documentation are visible according to the user role.
3. Do not connect an AI client yet. Complete the initial setup and access configuration first.