MCP Odoo Bridge Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOO_DB | No | Database name (auto-detected if not set) | |
| MCP_HOST | No | Host for HTTP transport | localhost |
| MCP_PORT | No | Port for HTTP transport | 8000 |
| ODOO_URL | Yes | Your Odoo instance URL (e.g., https://mycompany.odoo.com) | |
| ODOO_USER | No | Username (if not using API key) | |
| ODOO_YOLO | No | YOLO mode - bypasses MCP security (⚠️ DEV ONLY). Values: off, read, true | off |
| ODOO_API_KEY | No | API key for authentication (e.g., 0ef5b399e9ee9c11b053dfb6eeba8de473c29fcd) | |
| ODOO_TIMEOUT | No | Request timeout in seconds | 30 |
| MCP_TRANSPORT | No | Transport type: stdio or streamable-http | stdio |
| ODOO_PASSWORD | No | Password (if not using API key) | |
| ODOO_MAX_RECORDS | No | Default max records per query | 100 |
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 |
|---|---|
| search_recordsA | |
| get_recordB | |
| count_recordsA | |
| list_modelsA | |
| get_model_fieldsB | |
| create_recordA | |
| update_recordB | |
| delete_recordB | |
| execute_methodA | |
| get_record_nameC | |
| search_and_read_oneA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_models | List all models enabled for MCP access |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose with no ambiguity. Core CRUD operations (create_record, get_record, update_record, delete_record) are separate from search operations (search_records, search_and_read_one, count_records), metadata tools (list_models, get_model_fields), and specialized utilities (execute_method, get_record_name). The descriptions clearly differentiate each tool's specific function.
All tools follow a consistent verb_noun naming pattern throughout (e.g., count_records, create_record, search_records). The naming is perfectly uniform with no deviations in style or convention, making the tool set highly predictable and readable.
With 11 tools, this server is well-scoped for its purpose as an Odoo bridge. It provides comprehensive coverage of database operations (CRUD, search, count), metadata access, and specialized utilities without being overwhelming. Each tool earns its place in the set.
The tool surface provides complete CRUD/lifecycle coverage for the Odoo domain with no obvious gaps. It includes all essential operations (create, read, update, delete, search, count), metadata tools for discovery, and specialized utilities like execute_method for custom actions. The set enables full agent workflows without dead ends.