Odoo Devkit

Token-efficient MCP server for Odoo 17/18/19 development.

odoo-devkitgives AI assistants structured access to your Odoo codebase for discovery, search, model/view analysis, XML checks, and scaffolding patches.

- Fast module and code discovery across addons roots
- Model surface inspection (fields, methods, views, actions, menus, security)
- View inheritance navigation (find_view_chain, inherited views, field usage)
- Patch scaffolding for common Odoo tasks (models, views, actions, menus, security, wizards, reports)
- XML validation for view structure and field references
- Web dashboard that starts with the MCP server (Serena-style flow)
- Layered config: global + project override

- Python 3.10+
- uv(recommended)
- ripgrep(rg) for fast search

# Ubuntu/Debian sudo apt install ripgrep # macOS brew install ripgrep

git clone https://github.com/VatsalChauhan36/odoo-devkit.git cd odoo-devkit uv sync uv run odoo-devkit --help

You can configure roots and defaults via environment variables, global config, and project config.

- Global config:~/.odoo-devkit/config.json
- Project config:<project-root>/.odoo-devkit/project.json
- Global config
- Project override (if project root is detected)
- ODOO_MCP_PROJECT_ROOT
- nearest ancestor containing.odoo-devkit/project.json
- nearest ancestor containing.git

Addons roots are resolved with this priority:
- ODOO_MCP_ROOTS
- saved config (rootsin global/project config)
- Custom addons
- Odoo server addons
- Odoo base addons

export ODOO_MCP_ROOTS="/path/to/custom-addons:/path/to/odoo/addons:/path/to/odoo/odoo/addons"

$env:ODOO_MCP_ROOTS = "C:\custom-addons;C:\odoo\addons;C:\odoo\odoo\addons"

export ODOO_MCP_DOCS_PATH="/path/to/odoo/documentation"

The dashboard starts with the MCP server by default.

- open_browser
- enable_dashboard
- dashboard_host

uv run odoo-devkit --no-dashboard uv run odoo-devkit --dashboard-host 0.0.0.0 uv run odoo-devkit --no-open-browser uv run odoo-devkit --project-root /path/to/project

If browser auto-open is skipped (for example, headless Linux), use the MCP toolopen_dashboard.

Then this preview will render automatically:

These flags are intentionally kept for backward compatibility and are ignored:

They emit warnings and do not affect runtime behavior.

{ "mcpServers": { "odoo-devkit": { "type": "stdio", "command": "uv", "args": [ "run", "--directory", "/path/to/odoo-devkit", "odoo-devkit", "--project-root", "/path/to/your/project" ] } } }

{ "mcpServers": { "odoo-devkit": { "command": "uv", "args": [ "run", "--directory", "/path/to/odoo-devkit", "odoo-devkit", "--project-root", "/path/to/your/project" ] } } }

- list_modules
- list_custom_modules
- get_module_manifest
- get_module_structure
- glob_odoo_files
- read_file_lines
- search_odoo_code
- search_odoo_docs

- inspect_model_surface
- find_model_definition
- get_model_fields
- find_method_definition
- find_view_definition
- find_inherited_views
- find_view_by_model
- find_view_chain
- find_field_in_views
- validate_view_xml

- find_action_by_model
- find_menu_hierarchy
- find_security_access_for_model

- scaffold_model_patch
- scaffold_inherit_model_patch
- scaffold_view_inherit_patch
- scaffold_views_patch
- scaffold_action_patch
- scaffold_menu_patch
- scaffold_security_access_patch
- scaffold_record_rule_patch
- scaffold_wizard_patch
- scaffold_report_patch
- manifest_update_patch
- init_update_patch

- run_module_upgrade
- execute_rpc
- check_rpc_connection
- open_dashboard
- Start withlist_custom_modulesandget_module_structure
- Narrow withsearch_odoo_code(module_filter,glob)
- Useinspect_model_surfacefor model-level orientation
- Use view tools for inheritance-aware XML navigation
- Use scaffold tools to generate safe patches before applying

SetODOO_MCP_ROOTSor save roots in dashboard config (global/project).

- Checkopen_browsersetting
- Use--open-browserto force when supported
- On headless Linux, open URL manually or callopen_dashboard

- Verify path in--directory
- Re-runuv sync
- Runuv run odoo-devkit --helplocally

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Structured .aide spec files that give AI agents progressive disclosure into your codebase architecture. 6 MCP tools, 8 slash commands, TUI wizard, multi-IDE support.

An MCP server that enforces rules from markdown files for AI agents. This is a zero-tool version that requires an external rules file.

Automatic documentation updates from agents, and codebase conventions to reduce token usage.

Paid remote MCP for ZeroLang, structured receipts, usage logs, and audit-ready JSON evidence.

Local stdio MCP server that lets AI coding agents read and maintain structured architecture, rules, and decisions directly from your repository.

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

Official Context7 MCP server that brings up-to-date, version-specific library documentation and code examples into AI coding prompts.

Remote, no-auth MCP server providing AI-powered codebase context and answers

Official Svelte MCP server, provides docs and suggestions on the generated code.

Execute any LLM-generated code in the YepCode secure and scalable sandbox environment and create your own MCP tools using JavaScript or Python, with full support for NPM and PyPI packages