odoo-model-mcp

# odoo-model-mcp MCP server that exposes Odoo's model registry (fields, inheritance, methods) without needing a database connection. Point it at any Odoo project directory and get instant, structured answers about models, fields, method override chains, and inheritance graphs — powered by Odoo's own `MetaModel` registry loaded in-memory. > **Status:** Pre-alpha (0.1.0a1). Works with Odoo 16–19. ## How it works 1. **MCP server** (this package) receives tool calls via stdio. 2. It auto-detects the Odoo project structure (odoo-bin, addons paths, venv). 3. A **persistent worker subprocess** is spawned in the project's own Python venv, loading the full model registry once (~4 seconds). 4. Subsequent queries are served over a Unix domain socket in **1–15 ms**. 5. Workers auto-shutdown after 10 minutes of inactivity. Each project gets its own isolated worker process, so you can work with multiple Odoo versions simultaneously without conflicts. ## Installation ```bash # With uv (recommended) uv tool install odoo-model-mcp # With pip pip install odoo-model-mcp ``` ## Usage with Claude Code Add to your `~/.claude.json` (global) or project `.claude/settings.local.json`: ```json { "mcpServers": { "odoo-model-registry": { "type": "stdio", "command": "odoo-model-mcp", "args": [] } } } ``` If installed with `uv` and not on PATH: ```json { "mcpServers": { "odoo-model-registry": { "type": "stdio", "command": "uv", "args": ["run", "--project", "/path/to/odoo-model-mcp", "odoo-model-mcp"] } } } ``` ## Tools All tools accept a `project_path` pointing to the root of an Odoo project. Addons paths and the Odoo source location are auto-detected from the project structure (or can be overridden with `addons_paths`). Modules can be excluded by name with `exclude_modules` (useful when a module has unresolvable Python dependencies). ### `detect_project_info` Detect an Odoo project's structure without loading the r…