odoo-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOO_DB | Yes | Database name | |
| ODOO_URL | Yes | URL of the Odoo instance, e.g., https://my-instance.odoo.com | |
| ODOO_API_KEY | No | API key (required for JSON-2 / Odoo 19+) | |
| ODOO_PASSWORD | No | Legacy password for Odoo <=18 if no API key | |
| ODOO_USERNAME | Yes | Username for authentication | |
| ODOO_SOURCE_PATH | No | Optional path to addons directory to unlock TIER_2 code intelligence |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| odoo_statusA | Report connection status, detected Odoo version, transport and capability tier. |
| odoo_list_modelsB | List installed models (optionally filtered by technical name substring). |
| odoo_model_schemaA | Full schema for a model: normalised field metadata plus the deterministic model->table->column mapping (how the class maps to the database). |
| odoo_map_model_to_tableC | Return only the model<->table<->column mapping for a model. |
| odoo_relationshipsB | Build a relationship graph across the given models. Returns edges and, optionally, a Mermaid ER diagram. |
| odoo_searchC | Search and read records. |
| odoo_countC | Count records matching a domain. |
| odoo_access_rulesC | Return ACLs (ir.model.access) and record rules (ir.rule) for a model. |
| odoo_execute_methodC | Call a model method. Read-only methods are always allowed; mutating methods require ODOO_ENABLE_WRITES=1. |
| odoo_list_modulesB | List modules discovered in the configured source tree (ODOO_SOURCE_PATH). |
| odoo_module_dependency_diagramA | Mermaid flowchart of module dependencies from manifests. |
| odoo_inheritance_diagramA | Mermaid flowchart of model inheritance/extension/delegation across the source. |
| odoo_model_sourceC | Return the source-derived definition(s) of a model and a class diagram. |
| odoo_detect_driftA | Compare a model's SOURCE fields against the LIVE database and report drift (Studio/manual fields, un-upgraded modules, type mismatches). Needs both the source tree (TIER_2) and a live connection (TIER_0). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose, from querying records to exploring schema and code. There is no overlap; even similar functions like search and count are differentiated by operation. An agent can easily select the correct tool.
All tools follow a consistent pattern: 'odoo_' prefix followed by lowercase words separated by underscores. The names are descriptive and maintain a uniform style, making them predictable for an agent.
With 14 tools, the set is well-scoped for an Odoo agent. It covers essential areas like schema introspection, data querying, and code analysis without being overwhelming or too sparse.
The toolset covers major Odoo operations but lacks direct record CRUD tools (create, update, delete). However, odoo_execute_method can handle mutations, and the focus on analysis is clear. Minor gap but still robust.