Skip to main content
Glama
Sign In
openmausbot-cua-mcp

openmausbot-cua-mcp

by thestandard-production
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openmausbot-cua-mcp

No user-submitted related servers found.

    Related Servers

    • AKIMCP

      mMatuda96
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables web-based AI clients like Claude, ChatGPT, and Grok to securely operate a local machine through OAuth-gated MCP tools covering files, shell, Git, databases, browser automation, and background tasks.
      MIT

    • AKIMCP

      AkiraChaudhry31897
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables web-based AI clients such as Claude, ChatGPT, Grok, and Postman to securely operate a local machine through a single OAuth-gated MCP endpoint exposing 38 governed tools. Covers file read/write/edit, whitelisted shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost fetching, clipboard, notifications, port management, and Postman control.
      MIT

    • Codex Harness MCP

      2091k
      F
      license
      Not graded
      quality
      B
      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.
      -

    • AKIMCP

      Linda24064
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables web-based AI clients like Claude, ChatGPT, and Grok to securely operate a local machine through an OAuth-gated MCP endpoint, covering files, shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, ports, clipboard, notifications, and Postman. Exposes 38 governed tools with a strict command whitelist, folder allowlisting, and rate limiting so browser chats can build projects, inspect databases and local APIs, and manage long-running jobs without granting unrestricted shell access.
      MIT

    • aki-mcp-sv

      henrymartin33
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes 38 OAuth-gated tools over one MCP endpoint so web-based AI clients like Claude, ChatGPT, and Grok can read and edit local files, run whitelisted shell commands, search content, use Git, SQLite, browser automation, DevTools, clipboard, notifications, ports, and background jobs on your own machine. A strict command whitelist and folder restrictions keep the local operating surface governable and safe by default.
      -

    • AKIMCP

      fernandez16189
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a governed suite of 38 tools over a single OAuth-gated MCP endpoint, letting web AI chat clients such as Claude, ChatGPT, and Grok operate on a local machine — reading and editing files, running whitelisted shell commands, searching, querying SQLite, driving browsers and DevTools, managing background jobs, ports, and clipboard. Local IDEs and Postman can also connect directly over localhost for offline, low-latency access.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear separation between listing, mutating, and CUA-driver operations. Minor confusion is possible between openmausbot_api_health and openmausbot_status, and between the generic openmausbot_plan and the per-resource 'plan or apply' mutation tools, but descriptions mostly mitigate this.

    Naming Consistency3/5

    All tools share the openmausbot_ prefix, which helps, but verb patterns are mixed: list_bots vs get_companion_settings vs usage vs status, and cua_skills_status/cua_permissions_status/cua_check_update deviate from the list_/set_ convention. The naming is readable but not uniformly predictable.

    Tool Count3/5

    At 25 tools, this sits at the heavy end of the acceptable range. The count is somewhat justified by covering bot management, routines, webhooks, usage, companion settings, and the CUA-driver surface, but it feels like several smaller logical servers have been merged into one.

    Completeness3/5

    Routine lifecycle is well covered with upsert, enable/disable, run, and delete, and companion settings have get/set. However, webhooks are list-only with no create/update/delete, bots lack create/delete, and the CUA-driver tools only inspect and invoke rather than manage the driver itself, leaving notable gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources