Skip to main content
Glama

Related Servers

Alternatives to Odoo.sh MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that lets development agents work with Odoo.sh from their development environment, listing branches, watching builds, and streaming logs. It sits on top of the odouche Python library's public interface.
      7
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with Odoo ERP systems, providing comprehensive tools for searching, creating, updating, and managing Odoo records through a standardized interface.
      23
      GPL 3.0
    • A
      license
      B
      quality
      D
      maintenance
      Safety-first Model Context Protocol server for Odoo that enables AI assistants to safely inspect records, explain business data, prepare controlled changes, and rollback supported operations.
      7
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables seamless interaction with Odoo instances through the Model Context Protocol, supporting CRUD operations, custom method execution, and real-time updates. It offers versatile communication via stdio and HTTP protocols, including support for streaming and Server-Sent Events.
      8
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that provides 29 Git operations and advanced workflows, enabling AI assistants and developers to safely manage version control.
      30
      494 npm
      1
      ISC
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server integrating developer tools including Git control, document conversion, remote SSH execution, database operations, and utilities for automation and development productivity.
      1
      -

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: git operations, file operations, build/database/log queries, and shell execution are well separated. The only mild overlap is between get_project_info and get_system_info, both returning environment metadata, though their descriptions clarify the difference.

    Naming Consistency4/5

    The majority of tools follow a verb_noun pattern (get_project_info, list_branches, write_file, create_directory, execute_odoo_shell). The git_ prefix group (git_status, git_add, git_commit) is internally consistent, though git_status and git_pull deviate slightly from the verb-first style.

    Tool Count4/5

    19 tools is slightly above the ideal range but justified given the breadth of the domain (project/build management, databases, logs, shell, filesystem, and full git workflow). Each tool maps to a distinct capability rather than redundant variations.

    Completeness4/5

    The surface covers a full git lifecycle (status/add/commit/push/pull/checkout), file read/write/list/create, build triggering, logs, databases, and shell execution. Minor gaps exist, such as no file/directory delete or git diff, but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues