odooclaw-mcp
Provides tools for interacting with Odoo 18, including CRUD operations, sales, accounting, CRM, helpdesk, projects, and more.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@odooclaw-mcpFind sale order SO42 summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OdooClaw MCP
Standalone MCP (Model Context Protocol) server for Odoo 18 over stdio.
MCP name: io.github.nicolasramos/odooclaw-mcp
PyPI package: odooclaw-mcp
Official CLI: odooclaw-mcp
Backward-compatible aliases are also installed:
odoo-mcpodoo-mcp-serverodoo-18-mcp-server
Quick Start
1) Install
pip install odooclaw-mcpFrom source:
git clone https://github.com/nicolasramos/odooclaw-mcp.git
cd odooclaw-mcp
pip install -e .2) Configure environment
cp .env.example .envRequired:
ODOO_URL=https://yourcompany.odoo.com
ODOO_DB=your_database
ODOO_USERNAME=your_username
ODOO_PASSWORD=your_passwordOptional:
ODOO_MCP_DEFAULT_LIMIT=50
ODOO_MCP_MAX_LIMIT=80
LOG_LEVEL=INFO3) Validate and run
odooclaw-mcp --check-config
odooclaw-mcpAlternative:
python -m odoo_mcpMCP Client Configuration (stdio)
{
"mcpServers": {
"odoo": {
"command": "odooclaw-mcp",
"env": {
"ODOO_URL": "https://yourcompany.odoo.com",
"ODOO_DB": "your_database",
"ODOO_USERNAME": "your_username",
"ODOO_PASSWORD": "your_password",
"ODOO_MCP_DEFAULT_LIMIT": "50",
"ODOO_MCP_MAX_LIMIT": "80"
}
}
}
}Tool call payload contract
When calling tools through the MCP protocol, arguments must be wrapped in a
top-level payload object.
Valid shape:
{
"name": "odoo_search",
"arguments": {
"payload": {
"model": "res.partner",
"domain": [["customer_rank", ">", 0]],
"limit": 3
}
}
}If payload is omitted, validation fails with an error equivalent to
Field required: payload.
Scope
85 MCP tools for Odoo operations (CRUD + business actions + migration workflows)
Pydantic validation for all tool payloads
Odoo 18 compatibility helpers (customer_rank / supplier_rank / payment_state)
Security guards (model allowlist, denylisted fields, action guard, unlink blocked)
Structured logging and audit actions
Available Tools
The server currently exposes 85 MCP tools.
Note: the grouped tables below focus on common/high-value tools. Use MCP
list_toolsto inspect the full live tool catalog for your installed version.
Core record operations
Tool | Purpose |
| Search records in an allowed model using Odoo domain syntax. |
| Read selected fields from specific record IDs. |
| Combined search + read for efficient retrieval. |
| Create a new record in an allowed model. |
| Update existing records in an allowed model. |
| Invoke an Odoo model method such as |
| Return a compact, human-friendly summary for a record. |
Partners, sales, and CRM
Tool | Purpose |
| Find a customer or vendor by name, VAT, or email. |
| Get a partner overview with useful business context. |
| Search sale orders by name, partner, or state. |
| Retrieve a sale order summary including lines. |
| Create a quotation / sale order with product lines. |
| Confirm a quotation into a sale order. |
| Create a CRM lead / opportunity. |
Accounting, purchasing, and payments
Tool | Purpose |
| Create a purchase order from partner and line data. |
| Create a vendor bill. |
| Find posted invoices or bills pending payment using Odoo 18 semantics. |
| Get a detailed summary of an invoice or bill. |
| Register a payment for a specific invoice. |
Projects, activities, and chatter
Tool | Purpose |
| Search project tasks by name, project, or stage. |
| Create a new project task. |
| Update task stage, assignee, or deadline. |
| Schedule an activity on a record. |
| List pending activities, optionally filtered by model or assignee. |
| Mark an activity as completed. |
| Post a chatter message on a record. |
| Create a summary-style activity for follow-up. |
| Close an activity and record the reason. |
| Log a timesheet entry for a project or task. |
Support, contracts, stock, and instance capabilities
Tool | Purpose |
| Report which modules and capabilities are available in the connected instance. |
| Create a helpdesk ticket directly. |
| Create a helpdesk ticket linked to a partner. |
| Prepare a draft support email from a ticket context. |
| Add a line to a contract. |
| Replace an existing contract line with a new one. |
| Close a contract line with a reason and close date. |
| Inspect stock quantities for a product. |
| Create a meeting or appointment with attendees. |
Introspection
Tool | Purpose |
| Inspect the fields and schema of a model such as |
Available Resources
The server also exposes 5 MCP resources for discovery and context:
Resource | Purpose |
| Odoo 18 field reference for common model/domain pitfalls such as |
| JSON list of models currently allowed by the security policy. |
| Technical schema for a specific Odoo model. |
| JSON summary of a specific record. |
| Summary of the chatter history for a specific record. |
Guardrails and Runtime Behavior
Uses standard Odoo JSON-RPC endpoints; it does not depend on OdooClaw delegation.
Tool payloads are validated with Pydantic before execution.
Model access is restricted by an allowlist defined in the server configuration.
Sensitive write fields are denylisted and
unlinkis blocked.Search-style tools use default and maximum limits (
ODOO_MCP_DEFAULT_LIMIT,ODOO_MCP_MAX_LIMIT).sender_idis treated as audit/context metadata; execution runs as the authenticated Odoo session user.Some tools require the corresponding Odoo apps/modules to be installed (CRM, Helpdesk, Projects, Contracts, Inventory, etc.).
Security Model
The server uses standard Odoo JSON-RPC endpoints and executes operations as the configured Odoo session user.
For production, use a dedicated least-privilege Odoo account.
Production Notes
This is a
stdioMCP server, not an HTTP API service.Docker/Compose support is mainly for packaging or controlled runtime scenarios.
In normal usage, your MCP client launches the server process directly.
Keep Odoo credentials in environment variables or a secrets manager.
Known Limitations
One Odoo credential context per MCP process.
ODOO_DBis currently required by the authentication flow.Some tools require specific Odoo apps/modules (CRM, Helpdesk, Project, etc.).
Designed for Odoo 18 field semantics.
Development
pip install -e .[dev]
ruff check src tests
black --check src tests
mypy src --ignore-missing-imports
pytest tests -v
python -m build
twine check dist/*Docs
License
MIT - see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nicolasramos/odooclaw-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server