Skip to main content
Glama
RS-Nocsi

codex-cua-mcp

by RS-Nocsi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-cua-mcp

No user-submitted related servers found.

    Related Servers

    • Windows-MCP

      StepByStep-1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Windows operating systems through native UI automation, file navigation, application control, and system commands. Provides seamless integration between LLMs and Windows environments for tasks like clicking, typing, launching apps, and capturing desktop state.
      MIT

    • win-computer-use

      Regigicas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to control a Windows desktop via screenshots, mouse, keyboard, and window/display enumeration, reusing the native binding from the Claude desktop app.
      MIT

    • PyWinAuto MCP

      walkzzz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Windows GUI automation through the Model Context Protocol, providing tools, workflows, and generative capabilities for natural language-driven interaction with desktop applications.
      MIT
    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.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: window management, input actions, app launching, and element manipulation. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., activate_window, get_window_state). No mixing of styles or irregular naming.

    Tool Count5/5

    13 tools cover a well-scoped set of GUI automation operations (window control, input, app management), neither too few nor excessive for the domain.

    Completeness4/5

    The tool surface covers core actions (launch, list, navigate, input, state capture). Minor gaps like explicit screenshot-only or element waiting could exist but the set is largely complete for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources