Skip to main content
Glama
marcelo-m7

Monynha Odoo MCP

by marcelo-m7

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MONYNHA_MCP_MODENoTransport mode. Use 'stdio' for the local profile or 'http' for the remote gateway.
MONYNHA_MCP_HTTP_HOSTNoInterface for the HTTP server behind a reverse proxy, normally '0.0.0.0'.
MONYNHA_MCP_PUBLIC_URLNoPublic HTTPS MCP resource URL, for example 'https://mcp.example.com/mcp'.
MONYNHA_ODOO_KEY_LOCALNoSecret value for the local Odoo API key referenced by MONYNHA_MCP_LOCAL_SECRET_REF.
MONYNHA_MCP_OIDC_ISSUERNoTrusted external OIDC issuer for the remote HTTP gateway.
MONYNHA_ODOO_KEY_<NAME>NoSecret value referenced by each configured Odoo connection secret ref, using the connection-specific NAME suffix.
MONYNHA_MCP_DATABASE_URLNoPostgreSQL SQLAlchemy URL used by the remote HTTP gateway. Store as a managed secret.
MONYNHA_MCP_OIDC_AUDIENCENoOIDC audience. Must equal MONYNHA_MCP_PUBLIC_URL.
MONYNHA_MCP_OIDC_JWKS_URLNoHTTPS URL for the OIDC issuer's signing keys.
MONYNHA_MCP_LOCAL_ODOO_URLNoOdoo URL used by the local stdio profile.
MONYNHA_MCP_ALLOWED_ORIGINSNoOptional JSON array of trusted browser HTTPS origins. Does not replace OIDC authentication.
MONYNHA_MCP_CALLS_PER_MINUTENoPer principal/connection/operation rate limit. Default is 60.60
MONYNHA_MCP_LOCAL_SECRET_REFNoSecret reference for the local Odoo API key, for example 'env:MONYNHA_ODOO_KEY_LOCAL'.
MONYNHA_MCP_LOCAL_PRINCIPAL_IDNoLocal principal identifier used by the stdio profile.
MONYNHA_MCP_MAX_RESPONSE_BYTESNoMaximum Odoo response size in bytes. Default is 2 MiB.2097152
MONYNHA_MCP_LOCAL_CONNECTION_IDNoLocal Odoo connection identifier used by the stdio profile.
MONYNHA_MCP_MAX_CONCURRENT_PER_CONNECTIONNoPer-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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 11 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues