Odoo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| odoo_serverA | Control the Odoo server for the active project. action: start | stop | restart | status | shell (shell prints the command to open an interactive shell). |
| odoo_modulesA | Update/install/test Odoo modules in the active project. action: update | install | frontend | test. 'modules' is a comma-separated list (required for update/install/frontend; optional for test = all). Output is filtered to errors/warnings; use odoo_info action=logs for the full log. |
| odoo_projectA | Manage projects and their databases. action: list (projects + active one) | switch (activate odoo-.conf and restart; also changes the running Odoo 18/19) | new (scaffold a new project) | import (load a backup into the active DB) | fresh (reset the active DB to a fresh one initialized with base, + 'modules') | stream (stream a remote nellika.sh/tcff Odoo db+filestore over SSH into the active project). DESTRUCTIVE: import/fresh/stream drop the active DB; new creates/recreates the named DB. |
| odoo_infoB | Inspect the active project. action: logs (tail the full odoo.log) | config-path | project-config | project-dir | addons-dir (active core source: _odoo18 or _odoo19) | enterprise-dir. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| odoo-help | Get help with Odoo management commands |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools are split into clearly distinct domains: server control, module operations, project inspection, and database/project management. Mild overlap remains because odoo_project=switch performs a restart and odoo_modules refers to odoo_info=logs for full output, but the descriptions prevent serious confusion.
All tool names follow the same odoo_<noun> snake_case pattern, making the namespace easy to predict. The subactions are lowercase and consistent enough within each tool.
Four tools is within the ideal range and each tool represents a meaningful high-level area of Odoo work. No tool feels redundant; the small count keeps the surface navigable while covering server, module, info, and project concerns.
Core workflows are covered: starting/stopping the server, updating/installing/testing modules, inspecting logs/config, and managing project databases. Obvious gaps include no module scaffolding, no project deletion, and no database export/backup, but these are workable edge cases rather than core dead ends.