Skip to main content
Glama
odoo-model-mcp
by bemade

Related Servers

Alternatives to odoo-model-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      A bridge server that provides access to an Odoo shell environment, allowing execution of Python code within an Odoo database context for model introspection and database operations.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables developers to analyze Odoo errors, inspect addons and manifests, statically validate XML views, Python models, and security files, run unified addon health checks, and verify live metadata through read-only XML-RPC.
      8
      LGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables bounded, read-only code-graph search, neighbor/impact tracing, and architecture queries through a local offline gateway, while keeping source contents and mutation operations out of model-callable tools.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that enables AI assistants to query Odoo instances via XML-RPC, supporting search, read, count, and field inspection without requiring custom modules.
      56 PyPI
      1
      Mozilla Public 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to live Odoo instances over the Model Context Protocol so they can list available models and search, read, or write records such as contacts and invoices. It can run in a fast full-access mode or a hardened mode restricted to a whitelist of models with per-operation permissions and API-key authentication.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to interact with Odoo models through generic read and write tools, with read-only mode by default and Odoo ACLs as the authority.
      5
      34 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Odoo model introspection: listing vs searching, model-level vs field-level vs method-level detail, graph relationships, bulk export, and project detection. No overlap or ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with either verb_noun (list_models, search_models, dump_registry, detect_project_info) or noun_info/noun_graph (model_info, field_info, model_graph, method_overrides). The style is uniform and predictable.

    Tool Count5/5

    8 tools is well-scoped for an Odoo model introspection server. Each tool addresses a clear need without redundancy, and the count is within the ideal 3-15 range.

    Completeness5/5

    The tool surface covers the full lifecycle of model exploration: discover (list_models, search_models, detect_project_info), inspect (model_info, field_info, method_overrides), understand relationships (model_graph), and bulk ingest (dump_registry). No obvious gaps for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing