Skip to main content
Glama
thestandard-production

openmausbot-cua-mcp

Related Servers

Alternatives to openmausbot-cua-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI clients to invoke CLI-driven agent tools over Streamable HTTP, including shell execution, file operations, patching, image viewing, web search, and nested agent tasks, with permission modes and real-time progress streaming.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables browser-based AI chat interfaces to use local MCP tools by injecting a tool-call protocol into the page and executing approved filesystem, shell, and downstream MCP tool calls from a local daemon.
      352 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are clearly distinct, especially the list/describe/call cua-driver trio and the get/set companion settings pair. However, the three status-style tools (openmausbot_status, openmausbot_cua_skills_status, openmausbot_cua_permissions_status) are similar enough that an agent could initially struggle to pick the right one without reading descriptions carefully.

    Naming Consistency4/5

    The openmausbot_ prefix and generally verb_noun structure make the set predictable. Minor inconsistencies exist: some tools use bare noun-style names like openmausbot_status, and set_companion_setting uses singular while get_companion_settings uses plural.

    Tool Count5/5

    Nine tools is well-scoped for this server's purpose: environment/status checks, companion settings access, and discovery/invocation of cua-driver tools. Each tool has a distinct role and none feel redundant.

    Completeness4/5

    Core workflows are covered: checking daemon health, permissions, skills, release channel, reading/updating settings, and listing/describing/calling cua tools. The surface is slightly check-only around updates and skills—there is no install/update/enable action—but that appears intentional and is not a fatal gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues