Skip to main content
Glama
Odoo Developer Assistant MCP

Odoo Developer Assistant MCP

by pks0204

Related Servers

Alternatives to Odoo Developer Assistant MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      AI-powered Odoo engineering platform providing static analysis, domain knowledge, and 14 MCP tools for code review, model exploration, and security auditing of Odoo modules.
      18 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only inspection of Odoo production/staging data over JSON-RPC, letting Cursor list, search, read, and explore records and installed modules. A single instance serves several Odoo servers via profiles, with whitelisted ORM methods and credentials kept out of config files.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Odoo databases via XML-RPC and JSON-RPC for performing CRUD operations and managing modules. It supports advanced features like domain-based searching, field metadata inspection, and administrative task execution.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe, local DevOps inspection through a JSON-lines server with schema validation, path isolation, and redaction, supporting read-only Git operations, Kubernetes YAML validation, Terraform plan summaries, and sanitized log analysis.
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation3/5

    The per-file analyzers (XML, Python, security) are clearly distinct, but inspect_odoo_module, validate_odoo_manifest, and check_odoo_addon_health all take the same addon_path argument and examine manifest/dependency concerns, with health subsuming the other two. An agent must read descriptions carefully to choose between inspect vs validate vs the full health audit.

    Naming Consistency5/5

    Every tool follows a predictable verb_odoo_noun snake_case pattern (analyze_*, inspect_*, validate_*, check_*, verify_*) and uses 'odoo' as the consistent domain token. No mixed conventions or casing irregularities.

    Tool Count5/5

    Eight tools is well within the sweet spot and each maps to a distinct artifact type or workflow stage (manifest, XML, Python, security, error, aggregate audit, live verification). Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers static analysis across the major addon artifact types plus an aggregate health audit and live XML-RPC verification, which is strong lifecycle coverage for a developer assistant. Gaps remain: no scaffolding/module creation, no JS/OWL asset analysis, no automated fix application, and no i18n or test-related checks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues