odoo

This MCP server provides AI-assisted control and management for an Odoo development environment. It exposes 19 tools that let you start, stop, restart, and check the status of the Odoo server; install, update, and manage Odoo modules; perform frontend module updates with automatic server restarts; run tests with optional filters; switch and list databases; and fetch logs. In addition, there are directory and configuration helpers to locate project directories, core addons, and config files. These tools enable consistent, dialogue-driven management of Odoo projects across conversations, making it practical for AI assistants to orchestrate complex development workflows.

To use the tools, connect your MCP-enabled assistant (such as Claude Desktop) to the Odoo MCP server. For Claude Desktop, configure the MCP server entry with command set to node and point the path to the built index.js file. Once connected, you can issue natural language commands like: start the Odoo server, update specific modules, run tests for a given module, switch databases, or retrieve the latest logs. The tools map to actions such as odoo_start, odoo_stop, odoo_update_modules, odoo_run_tests, odoo_switch_database, and odoo_get_logs, among others, enabling scripted or conversational automation of Odoo development tasks.

Prerequisites:

• Node.js 16+ installed on your system
• A cloned copy of the Odoo MCP Server repository
• An Odoo development environment with manage_odoo.sh available if required by your workflow

Step-by-step install:

1. Install dependencies

cd ~/git/odoo-mcp-server
npm install

2. Build the TypeScript project (if applicable)

npm run build

3. Ensure the built index is available at the path referenced by your MCP config. For Claude/Desktop integration, you typically point to the build/index.js file. If you haven’t built yet, run:

npm run build

4. Configure your MCP client (e.g., Claude Desktop) to connect to the server by specifying the command and path to the built entry point. Example config snippet:

{
  "mcpServers": {
    "odoo": {
      "command": "node",
      "args": ["/path/to/odoo-mcp-server/build/index.js"]
    }
  }
}

5. Start the MCP server process if you run it directly (optional depending on your setup):

node build/index.js

6. Verify the server is responsive by invoking a basic tool, such as listing databases or checking server status, and ensure the MCP client can access the toolset.

Tips and considerations:

• The server assumes an Odoo development environment is present and accessible; ensure paths and scripts referenced by tools (e.g., manage_odoo.sh) exist and are executable.
• If you modify DEFAULT_CONFIGS and add new Odoo versions, remember to rebuild the project with npm run build.
• Common issues often involve incorrect paths to the built index.js, missing dependencies, or Claude Desktop not correctly pointing to the MCP entry. Double-check the build directory exists and that your MCP client’s config matches the actual path to build/index.js.
• For log retrieval, odoo_get_logs returns the last N lines; ensure the Odoo logging mechanism writes to a known log file accessible by the MCP server.
• If environment-specific variables are needed (such as custom Odoo paths or database configurations), consider extending the mcp_config with environment variables under an env object if your hosting environment supports it.