Skip to main content
Glama
avanserv

odouche-mcp

by avanserv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to odouche-mcp

No user-submitted related servers found.

    Related Servers

    • Panda Odoo MCP Server

      pandeussilvae
      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

    • Raccoon MCP

      luoluoluo22
      A
      license
      C
      quality
      C
      maintenance
      A local-first Model Context Protocol server that enables AI-assisted development through scoped file access, opt-in shell and process execution, Git automation, development pipelines, and optional Windows desktop and Android/ADB tools. It supports streamable HTTP and stdio transports with secure local-only defaults.
      105
      MIT

    • stela-mcp

      Sachin-Bhat
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.
      14
      1
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation4/5

    The tools are mostly distinct by resource and action: project overview/settings, branches, builds, revisions, mails, logs and session each have clear roles. The build-centric tools (get_build, get_build_revision, list_builds, wait_for_build) are close enough that an agent may need to read descriptions carefully, but they are not truly overlapping.

    Naming Consistency5/5

    All tool names use consistent snake_case verb_noun or verb_preposition_noun patterns: get_*, list_*, read_*, and wait_for_*. There is no mixing of camelCase or vague standalone verbs.

    Tool Count4/5

    At 16 tools, the server is slightly above the typical 3-15 well-scoped range but still reasonable for a rich read-only inspection domain. Each tool maps to a coherent project, branch, build, mail, log or session concern rather than feeling padded.

    Completeness4/5

    The surface covers the main read-only inspection workflows comprehensively: projects, settings, members, audit logs, branches, builds, revisions, history, mails, logs, and polling. The main limitations are Odoo.sh-imposed bounds and the absence of any write or mutation operations, which appears intentional for this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources