Skip to main content
Glama
deenesjakoruzh
plgonzalezrx8

odoo-mcp

by plgonzalezrx8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

odoo-mcp

Docker-First FastMCP-Server für Odoo 19 JSON-2-Integrationen.

Die Laufzeitumgebung stellt eine gemeinsame Server-Factory bereit, die sowohl für stdio- als auch für HTTP-Transporte verwendet wird. Odoo-spezifische Tools können sich bei dieser Factory über odoo_mcp.tools.register_tools(server, config) oder ein kompatibles Registry-Modul registrieren.

Schnellstart

  1. Kopieren Sie die Umgebungsvorlage:

    cp .env.example .env

  2. Bearbeiten Sie .env mit Ihrem Odoo-Endpunkt und Ihren Anmeldedaten.

  3. Starten Sie den HTTP-Server:

    docker compose up --build

  4. Überprüfen Sie die lokale Bereitschaft:

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

Der Standard-MCP-Endpunkt ist http://localhost:8000/mcp.

Related MCP server: odoo-mcp

Laufzeitbefehle

Ausführung über stdio für MCP-Clients, die den Serverprozess direkt starten:

odoo-mcp stdio

Ausführung über HTTP:

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

Bereinigte Konfiguration prüfen, ohne Geheimnisse preiszugeben:

odoo-mcp inspect-config

Lokale Prozessbereitschaft prüfen, ohne Odoo zu kontaktieren:

odoo-mcp healthcheck

Konfiguration

Variable

Zweck

ODOO_URL

Basis-URL für Odoo JSON-2-Aufrufe. Erforderlich für Odoo-API-Tools.

ODOO_DATABASE

Optionaler Odoo-Datenbankname.

ODOO_USERNAME

Optionaler Odoo-Benutzername.

ODOO_PASSWORD

Optionales Odoo-Passwort. Wird durch inspect-config maskiert.

ODOO_API_KEY

Optionaler Odoo-API-Schlüssel. Wird durch inspect-config maskiert.

JWT_SECRET

Optionales Geheimnis für zukünftige HTTP-Authentifizierungs-Middleware. Wird durch inspect-config maskiert.

MCP_HTTP_HOST

HTTP-Bind-Host. Standard ist 0.0.0.0.

MCP_HTTP_PORT

HTTP-Bind-Port. Standard ist 8000.

MCP_HTTP_PATH

HTTP-Endpunkt-Pfad. Standard ist /mcp.

MCP_LOG_LEVEL

Uvicorn-Log-Level. Standard ist info.

Entwicklung

Installieren und führen Sie Tests mit uv aus:

uv sync
uv run pytest

Statische Prüfungen, die von CI verwendet werden:

uv run ruff check .
uv run mypy

Docker ist der Ziel-Bereitstellungspfad, aber lokales Docker ist für Unit-Tests nicht erforderlich. Der Docker-Healthcheck verwendet odoo-mcp healthcheck, was die Verkabelung des Serverprozesses validiert, ohne externe Netzwerkaufrufe zu tätigen.

Integrationspunkte

Die gemeinsame Factory ist odoo_mcp.server.build_server(). Sie registriert immer ein lokales healthcheck-Tool und versucht dann, die Tool-Registrierung von folgenden Orten zu importieren:

  • odoo_mcp.tools.register_tools

  • odoo_mcp.tools.registry.register_tools

  • odoo_mcp.tools.odoo.register_tools

Kompatible Funktionen können entweder (server) oder (server, config) akzeptieren. Dies soll es ermöglichen, den Odoo-Client, das Schema und die Tool-Worker unabhängig voneinander zu implementieren, ohne die Laufzeit-Einstiegspunkte zu ändern.

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