Monynha Odoo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MONYNHA_MCP_MODE | No | Transport mode. Use 'stdio' for the local profile or 'http' for the remote gateway. | |
| MONYNHA_MCP_HTTP_HOST | No | Interface for the HTTP server behind a reverse proxy, normally '0.0.0.0'. | |
| MONYNHA_MCP_PUBLIC_URL | No | Public HTTPS MCP resource URL, for example 'https://mcp.example.com/mcp'. | |
| MONYNHA_ODOO_KEY_LOCAL | No | Secret value for the local Odoo API key referenced by MONYNHA_MCP_LOCAL_SECRET_REF. | |
| MONYNHA_MCP_OIDC_ISSUER | No | Trusted external OIDC issuer for the remote HTTP gateway. | |
| MONYNHA_ODOO_KEY_<NAME> | No | Secret value referenced by each configured Odoo connection secret ref, using the connection-specific NAME suffix. | |
| MONYNHA_MCP_DATABASE_URL | No | PostgreSQL SQLAlchemy URL used by the remote HTTP gateway. Store as a managed secret. | |
| MONYNHA_MCP_OIDC_AUDIENCE | No | OIDC audience. Must equal MONYNHA_MCP_PUBLIC_URL. | |
| MONYNHA_MCP_OIDC_JWKS_URL | No | HTTPS URL for the OIDC issuer's signing keys. | |
| MONYNHA_MCP_LOCAL_ODOO_URL | No | Odoo URL used by the local stdio profile. | |
| MONYNHA_MCP_ALLOWED_ORIGINS | No | Optional JSON array of trusted browser HTTPS origins. Does not replace OIDC authentication. | |
| MONYNHA_MCP_CALLS_PER_MINUTE | No | Per principal/connection/operation rate limit. Default is 60. | 60 |
| MONYNHA_MCP_LOCAL_SECRET_REF | No | Secret reference for the local Odoo API key, for example 'env:MONYNHA_ODOO_KEY_LOCAL'. | |
| MONYNHA_MCP_LOCAL_PRINCIPAL_ID | No | Local principal identifier used by the stdio profile. | |
| MONYNHA_MCP_MAX_RESPONSE_BYTES | No | Maximum Odoo response size in bytes. Default is 2 MiB. | 2097152 |
| MONYNHA_MCP_LOCAL_CONNECTION_ID | No | Local Odoo connection identifier used by the stdio profile. | |
| MONYNHA_MCP_MAX_CONCURRENT_PER_CONNECTION | No | Per-connection in-process concurrency limit. Default is 4. | 4 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_info_getA | Show supported backend and version. |
| connection_listB | List connections accessible to the authenticated client. |
| connection_testC | Check connectivity to an authorized Odoo instance. |
| model_listC | Find Odoo models available to this connection. |
| model_fields_getC | Read accessible field definitions of one model. |
| record_getC | Read selected Odoo record IDs. |
| record_searchC | Search records by Odoo domain and page through the results. |
| record_countC | Count Odoo records matching a domain. |
| record_aggregateC | Read grouped aggregates via the Odoo ORM. |
| record_createC | Create a record only when the connection policy allows it. |
| record_updateC | Update records only when the connection policy allows it. |
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 11 tools
Each tool targets a distinct Odoo operation: connection lifecycle, model introspection, or a specific record operation (create, update, get, search, count, aggregate). The record-oriented tools share a resource but have clearly separated semantics and input shapes, so an agent should not misselect. No two tools appear interchangeable.
All 11 tools follow a consistent noun_verb pattern (record_create, model_list, connection_test, server_info_get). Compound nouns like server_info and model_fields are handled predictably, with no mixing of camelCase, vague verbs, or inconsistent ordering.
Eleven tools is well-scoped for a generic Odoo MCP server covering connection checks, schema introspection, and core record operations. Each tool earns its place without obvious redundancy or filler.
The surface covers create, update, read, search, count, and aggregate, but there is no record_delete or bulk operation, leaving a notable gap in the CRUD lifecycle. Connection creation and model-level schema mutations are also absent, though those may be intentionally out of scope.