Odoo Boost
AI coding agents with deep introspection into running Odoo instances via MCP tools.
Inspired by Laravel Boost, Odoo Boost gives your AI coding assistant deep knowledge of your Odoo project — models, views, records, access rights, configuration, and more — plus Odoo-specific development guidelines and step-by-step skills.
Features
- 15 MCP Tools — Introspect models, views, records, access rights, config, routes, workflows, and more from a live Odoo instance
- 6 AI Agents — Claude Code, Cursor, Copilot, Codex, Gemini CLI, Junie
- Odoo Guidelines — Version-aware development best practices injected into your agent's context
- 8 Skills — Step-by-step guides for common Odoo development tasks (creating models, views, security, OWL components, etc.)
- Multi-version — Supports Odoo 17, 18, and 19
- Zero config on Odoo side — Connects via XML-RPC, no Odoo module installation needed
Installation
pip install odoo-boost
Or with uv:
uv pip install odoo-boost
You can also install it as a global CLI tool:
uv tool install odoo-boost
Quick Start
1. Run the install wizard
cd /path/to/your/odoo-project
odoo-boost install
The wizard will:
- Ask for your Odoo connection details (URL, database, username, password)
- Test the connection and detect the Odoo version
- Let you select which AI agents to configure
- Generate all necessary files (guidelines, MCP config, skills)
2. Verify the connection
odoo-boost check
Or with explicit credentials:
odoo-boost check --url http://localhost:8069 --database mydb --username admin --password admin
3. Start coding
Your AI agent is now configured. The MCP server starts automatically when your agent needs it. Try asking your agent:
"What models are available in this Odoo instance?" "Show me the fields on the res.partner model" "Search for all installed modules related to accounting"
Commands
| Command | Description |
|---|---|
odoo-boost install |
Interactive setup wizard |
odoo-boost check |
Test connection to Odoo |
odoo-boost update |
Re-generate files from saved config |
odoo-boost mcp |
Start the MCP server (stdio) |
odoo-boost --version |
Show version |
You can also run any command via python -m odoo_boost, e.g. python -m odoo_boost --version.
How It Works
┌─────────────────┐ stdio ┌─────────────────┐ XML-RPC ┌──────────────┐
│ AI Agent │◄──────────────►│ Odoo Boost │◄─────────────►│ Odoo │
│ (Claude, etc.) │ │ MCP Server │ │ Instance │
└─────────────────┘ └─────────────────┘ └──────────────┘
│ │
▼ │
Guidelines + 15 MCP Tools
Skills (md) (models, views, records,
config, access rights…)
Odoo Boost sits between your AI agent and your Odoo instance. It provides:
- MCP Tools — Your agent calls tools like
list_models,search_records,database_schemato understand your Odoo instance in real-time - Guidelines — Odoo development best practices are injected into your agent's context so it writes idiomatic code
- Skills — Step-by-step guides for common tasks (creating models, views, security rules, etc.)
Robust MCP Server Resolution
The generated MCP config files use the full path to the Python interpreter that has Odoo Boost installed, rather than relying on a bare odoo-boost command being available on PATH. This ensures the MCP server starts correctly regardless of how your AI agent spawns subprocesses.
For example, the generated .mcp.json for Claude Code looks like:
{
"mcpServers": {
"odoo-boost": {
"command": "/path/to/your/venv/bin/python",
"args": ["-m", "odoo_boost", "mcp"]
}
}
}
This means:
- The MCP server always runs in the correct Python environment
- No dependency on
PATHconfiguration or shell activation - Works with virtualenvs,
uv tool, and system installs alike
.gitignore
Generated files contain environment-specific paths and should generally not be committed. Add the following to your .gitignore:
# Odoo Boost
odoo-boost.json
CLAUDE.md
AGENTS.md
GEMINI.md
.mcp.json
.ai/skills/
.cursor/rules/odoo-boost.mdc
.cursor/mcp.json
.cursor/skills/
.vscode/mcp.json
.github/copilot-instructions.md
.github/skills/
.codex/
.gemini/settings.json
.agents/skills/
.junie/
Note: Only the files listed above are generated by Odoo Boost. Directories like
.github/and.vscode/may contain other project files — do not ignore the entire directory.
Documentation
- Getting Started — Full setup walkthrough
- MCP Tools Reference — All 15 tools with parameters and examples
- Agent Configuration — Supported agents and their generated files
- Configuration —
odoo-boost.jsonschema and CLI options - Guidelines — Bundled Odoo development guidelines
- Skills — Step-by-step development skills
- Contributing — How to add tools, agents, and skills
Supported Agents
| Agent | Guidelines | MCP Config | Skills |
|---|---|---|---|
| Claude Code | CLAUDE.md |
.mcp.json |
.ai/skills/ |
| Cursor | .cursor/rules/odoo-boost.mdc |
.cursor/mcp.json |
.cursor/skills/ |
| GitHub Copilot | .github/copilot-instructions.md |
.vscode/mcp.json |
.github/skills/ |
| OpenAI Codex | AGENTS.md |
.codex/config.toml |
.agents/skills/ |
| Gemini CLI | GEMINI.md |
.gemini/settings.json |
.agents/skills/ |
| Junie | .junie/guidelines.md |
.junie/mcp/mcp.json |
.junie/skills/ |
License
MIT
Metadata
Release files for odoo-boost 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| odoo_boost-0.4.1.tar.gz | 58.6 kB | With provenance | Details for odoo_boost-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_boost-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for odoo_boost-0.4.1-py3-none-any.whl |
Total release size: 121.6 kB
Release files / odoo_boost-0.4.1.tar.gz
| Download URL | odoo_boost-0.4.1.tar.gz |
|---|---|
| Size | 58.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70c7276e174ec271297f4b779a97c36887e587515e09c02117845b6fea7e96a0
|
|
BLAKE2b-256 checksum How to use checksums |
e5ae283755f5fb32bd95529c79d4044d2c4c5dcabe3042bda35bb556e23ea078
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 20, 2026.
Transparency logRelease files / odoo_boost-0.4.1-py3-none-any.whl
| Download URL | odoo_boost-0.4.1-py3-none-any.whl |
|---|---|
| Size | 63.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a304f6cc0b36ae21b031cb25cd2e2b609d282d21845f118870e45a09a9bf734
|
|
BLAKE2b-256 checksum How to use checksums |
b26315092b55675a483ed96c14a9d192608a120c65c49fe00723b0c184e36328
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 20, 2026.
Transparency logSecurity for odoo-boost 0.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for odoo_boost-0.4.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.