Odoo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOO_DB | No | Database name. | odoo_demo |
| ODOO_URL | No | Odoo base URL. | http://localhost:8069 |
| ODOO_USER | No | Login. | admin |
| ODOO_PASSWORD | No | Password or (better) an Odoo API key. | admin |
| ODOO_READ_ONLY | No | Set to true to remove all write tools. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Access to an Odoo 18 ERP: CRM leads/opportunities, customers (partners), sales orders and unpaid customer invoices. Amounts are in the record's currency (company currency for CRM). Writes are two-step: call a write tool without confirm to get a preview, show it to the user, and only call again with confirm=true once they approve.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_leadsA | List CRM leads and opportunities, highest expected revenue first. |
| search_partnersA | Find customers and contacts (Odoo partners) by name, email or phone. Partners are companies or individual people; individuals may belong to a company. |
| get_sales_ordersA | List sales orders and quotations, newest first, with customer, total and invoice status. |
| get_unpaid_invoicesA | List posted customer invoices that are not (fully) paid, oldest due date first. Includes amount still due and days overdue. Use for "who owes us money?" or "which invoices are overdue?". |
| pipeline_summaryA | Summarize the sales pipeline: number of opportunities and expected revenue per stage. |
| create_leadA | Create a new CRM lead in Odoo, in two steps. |
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 6 tools
Each tool targets a distinct resource or view: leads, partners, sales orders, unpaid invoices, pipeline aggregate, and lead creation. The only mild overlap is list_leads versus pipeline_summary, but one returns records and the other aggregates by stage, so the descriptions make the boundary clear.
Five of six names follow a clean verb_noun pattern (list_leads, search_partners, get_sales_orders, get_unpaid_invoices, create_lead). pipeline_summary is a noun-only outlier, but it is still readable and unambiguous.
Six tools is well-scoped for a CRM/sales assistant, with each tool covering a distinct question type (pipeline, contacts, orders, receivables, creation). No redundant or filler tools.
The surface is read-heavy with a single write path (create_lead): there is no update/advance lead, no close/won-lost action, no quotation or sales-order creation, and no invoice detail or payment marking. Core read workflows are covered, but lifecycle coverage is notably partial for a sales CRM.