Skip to main content
Glama
deenesjakoruzh
plgonzalezrx8

odoo-mcp

by plgonzalezrx8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

odoo-mcp

Servidor FastMCP orientado a Docker para integraciones con Odoo 19 JSON-2.

El tiempo de ejecución expone una fábrica de servidores compartida utilizada tanto por transportes stdio como HTTP. Las herramientas específicas de Odoo pueden registrarse en esa fábrica desde odoo_mcp.tools.register_tools(server, config) o un módulo de registro compatible.

Inicio rápido

  1. Copie la plantilla de entorno:

    cp .env.example .env

  2. Edite .env con su endpoint y credenciales de Odoo.

  3. Inicie el servidor HTTP:

    docker compose up --build

  4. Inspeccione la disponibilidad local:

    docker compose exec odoo-mcp uv run --no-sync odoo-mcp healthcheck

El endpoint MCP predeterminado es http://localhost:8000/mcp.

Related MCP server: odoo-mcp

Comandos de tiempo de ejecución

Ejecutar sobre stdio para clientes MCP que lanzan el proceso del servidor directamente:

odoo-mcp stdio

Ejecutar sobre HTTP:

odoo-mcp http --host 0.0.0.0 --port 8000 --path /mcp

Inspeccionar la configuración saneada sin exponer secretos:

odoo-mcp inspect-config

Comprobar la disponibilidad del proceso local sin contactar con Odoo:

odoo-mcp healthcheck

Configuración

Variable

Propósito

ODOO_URL

URL base para llamadas JSON-2 de Odoo. Requerido por las herramientas de la API de Odoo.

ODOO_DATABASE

Nombre opcional de la base de datos de Odoo.

ODOO_USERNAME

Nombre de usuario opcional de Odoo.

ODOO_PASSWORD

Contraseña opcional de Odoo. Redactada por inspect-config.

ODOO_API_KEY

Clave de API opcional de Odoo. Redactada por inspect-config.

JWT_SECRET

Secreto opcional para futuros middleware de autenticación HTTP. Redactado por inspect-config.

MCP_HTTP_HOST

Host de enlace HTTP. Por defecto 0.0.0.0.

MCP_HTTP_PORT

Puerto de enlace HTTP. Por defecto 8000.

MCP_HTTP_PATH

Ruta del endpoint HTTP. Por defecto /mcp.

MCP_LOG_LEVEL

Nivel de registro de Uvicorn. Por defecto info.

Desarrollo

Instale y ejecute pruebas con uv:

uv sync
uv run pytest

Comprobaciones estáticas utilizadas por CI:

uv run ruff check .
uv run mypy

Docker es la ruta de despliegue objetivo, pero no se requiere Docker local para las pruebas unitarias. La comprobación de salud de Docker utiliza odoo-mcp healthcheck, que valida la conexión del proceso del servidor sin realizar llamadas de red externas.

Puntos de integración

La fábrica compartida es odoo_mcp.server.build_server(). Siempre registra una herramienta healthcheck local, y luego intenta importar el registro de herramientas desde:

  • odoo_mcp.tools.register_tools

  • odoo_mcp.tools.registry.register_tools

  • odoo_mcp.tools.odoo.register_tools

Las funciones compatibles pueden aceptar (server) o (server, config). Esto tiene como objetivo permitir que el cliente de Odoo, el esquema y los trabajadores de herramientas se implementen de forma independiente sin cambiar los puntos de entrada del tiempo de ejecución.

Available Tools

1 tool
healthcheckA

Return local server readiness metadata.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description indicates a read-only operation returning metadata, which is typical for a healthcheck. However, without annotations, the description does not explicitly confirm non-destructive behavior or other traits like rate limits or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundant words, efficiently conveying the tool's purpose. It earns its place without any filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no parameters, no siblings), the description is nearly complete. The presence of an output schema reduces the need to detail return values, though 'metadata' is somewhat vague. It covers the essential purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds value by specifying the returned content ('readiness metadata'), which is beyond what the empty schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states the tool returns 'local server readiness metadata,' using a specific verb ('return') and a clear resource. No sibling tools exist, so differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage as a health check for monitoring server readiness, but provides no explicit when-to-use or when-not-to-use guidance. The lack of siblings reduces the need for alternatives, but the description misses contextual cues like frequency or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedhealthcheck
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The purpose of 'healthcheck' is clear and distinct.

Naming Consistency5/5

A single tool cannot be inconsistent with itself. The name 'healthcheck' is a reasonable single-word descriptor.

Tool Count1/5

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.

Completeness1/5

For an Odoo integration, a single healthcheck tool is severely incomplete, lacking any CRUD operations or domain-specific functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Odoo 18 MCP Server

    KKday-KevinChu
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Odoo 18 (JSON-RPC API) via MCP, supporting model exploration, CRUD operations, and secure API key authentication.
    Apache 2.0

  • odoo-mcp

    AleemHaider
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude to interact with Odoo through 12 MCP tools covering discovery, CRUD operations, and bulk import/export via XML-RPC.
    MIT

  • Odoo MCP Server

    SalimaTerbah
    F
    license
    Not graded
    quality
    C
    maintenance
    Exposes Odoo 19 ERP as MCP tools, enabling AI agents to query and act on CRM data (leads, semantic search) via natural language without custom integration.
    -

  • odoo-json2

    tylerjharden
    A
    license
    A
    quality
    B
    maintenance
    Enables interaction with Odoo 19 databases through the External JSON-2 API, allowing model operations such as search, read, create, write, and unlink via MCP tools.
    2
    MIT