odoo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOO_URL | Yes | Base URL for Odoo JSON-2 calls. Required by Odoo API tools. | |
| JWT_SECRET | No | Optional secret for future HTTP auth middleware. | |
| ODOO_API_KEY | No | Optional Odoo API key. | |
| MCP_HTTP_HOST | No | HTTP bind host. | 0.0.0.0 |
| MCP_HTTP_PATH | No | HTTP endpoint path. | /mcp |
| MCP_HTTP_PORT | No | HTTP bind port. | 8000 |
| MCP_LOG_LEVEL | No | Uvicorn log level. | info |
| ODOO_DATABASE | No | Optional Odoo database name. | |
| ODOO_PASSWORD | No | Optional Odoo password. | |
| ODOO_USERNAME | No | Optional Odoo username. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthcheckA | Return local server readiness metadata. |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The purpose of 'healthcheck' is clear and distinct.
A single tool cannot be inconsistent with itself. The name 'healthcheck' is a reasonable single-word descriptor.
The server is named for Odoo, a full-featured ERP system, but provides only a single health check endpoint. This is an extreme mismatch between scope and tool count.
For an Odoo integration, a single healthcheck tool is severely incomplete, lacking any CRUD operations or domain-specific functionality.