Skip to main content
Glama
deenesjakoruzh
plgonzalezrx8

odoo-mcp

by plgonzalezrx8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

odoo-mcp

Odoo 19 JSON-2 통합을 위한 Docker 우선 FastMCP 서버입니다.

런타임은 stdio 및 HTTP 전송 모두에서 사용되는 하나의 공유 서버 팩토리를 노출합니다. Odoo 전용 도구는 odoo_mcp.tools.register_tools(server, config) 또는 호환되는 레지스트리 모듈에서 해당 팩토리에 등록할 수 있습니다.

빠른 시작

  1. 환경 템플릿을 복사합니다:

    cp .env.example .env

  2. Odoo 엔드포인트와 자격 증명으로 .env를 편집합니다.

  3. HTTP 서버를 시작합니다:

    docker compose up --build

  4. 로컬 준비 상태를 확인합니다:

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

기본 MCP 엔드포인트는 http://localhost:8000/mcp입니다.

Related MCP server: odoo-mcp

런타임 명령

서버 프로세스를 직접 시작하는 MCP 클라이언트를 위해 stdio를 통해 실행합니다:

odoo-mcp stdio

HTTP를 통해 실행합니다:

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

비밀 정보를 노출하지 않고 정리된 구성을 검사합니다:

odoo-mcp inspect-config

Odoo에 연결하지 않고 로컬 프로세스 준비 상태를 확인합니다:

odoo-mcp healthcheck

구성

변수

목적

ODOO_URL

Odoo JSON-2 호출을 위한 기본 URL. Odoo API 도구에 필요합니다.

ODOO_DATABASE

선택 사항인 Odoo 데이터베이스 이름.

ODOO_USERNAME

선택 사항인 Odoo 사용자 이름.

ODOO_PASSWORD

선택 사항인 Odoo 비밀번호. inspect-config에 의해 가려집니다.

ODOO_API_KEY

선택 사항인 Odoo API 키. inspect-config에 의해 가려집니다.

JWT_SECRET

향후 HTTP 인증 미들웨어를 위한 선택 사항인 비밀 키. inspect-config에 의해 가려집니다.

MCP_HTTP_HOST

HTTP 바인드 호스트. 기본값은 0.0.0.0입니다.

MCP_HTTP_PORT

HTTP 바인드 포트. 기본값은 8000입니다.

MCP_HTTP_PATH

HTTP 엔드포인트 경로. 기본값은 /mcp입니다.

MCP_LOG_LEVEL

Uvicorn 로그 레벨. 기본값은 info입니다.

개발

uv를 사용하여 설치하고 테스트를 실행합니다:

uv sync
uv run pytest

CI에서 사용하는 정적 검사:

uv run ruff check .
uv run mypy

Docker가 대상 배포 경로이지만, 단위 테스트를 위해 로컬 Docker가 반드시 필요한 것은 아닙니다. Docker 상태 확인은 odoo-mcp healthcheck를 사용하며, 이는 외부 네트워크 호출 없이 서버 프로세스 연결을 검증합니다.

통합 지점

공유 팩토리는 odoo_mcp.server.build_server()입니다. 이 팩토리는 항상 로컬 healthcheck 도구를 등록한 다음, 다음 위치에서 도구 등록을 가져오려고 시도합니다:

  • odoo_mcp.tools.register_tools

  • odoo_mcp.tools.registry.register_tools

  • odoo_mcp.tools.odoo.register_tools

호환되는 함수는 (server) 또는 (server, config)를 허용할 수 있습니다. 이는 Odoo 클라이언트, 스키마 및 도구 작업자가 런타임 진입점을 변경하지 않고 독립적으로 작동할 수 있도록 하기 위함입니다.

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