Skip to main content
Glama
pironjulien

nexus-windows-codex

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to nexus-windows-codex

No user-submitted related servers found.

    Related Servers

    • screen-use

      tongriyaotxt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to see, locate UI elements, and operate any Windows desktop app through natural language, using accessibility-tree matching with optional vision-model fallback, plus an autonomous visual loop with introspection and meta-learning.
      3
      MIT

    • windows-gui-mcp

      dcl632
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to automate Windows desktop applications through semantic UI Automation instead of brittle coordinate clicks, with tools for discovering windows, finding controls by stable identifiers, and verifying actions.
      45 PyPI
      3
      MIT

    • ORVEX

      ujjawalsol
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive Windows desktop automation — opening and interacting with applications, native UI controls, keyboard/mouse input, files, processes, clipboard, and Chrome/Edge browsing via UI Automation and CDP. All actions pass through a safety policy with human approval, emergency stop, and deterministic verification.
      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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation3/5

    The core actions are mostly distinguishable: windows lists windows, look inspects one, act operates on the last looked window, and launch opens apps. However, the near-identical names windows and window are confusing, especially since window only closes a window rather than managing one generically. look also overlaps conceptually with windows because both are observation tools, though at different levels of detail.

    Naming Consistency2/5

    The set mixes plural/singular nouns (windows, window) with bare verbs (act, launch, look), and act is especially vague on its own. There is no predictable verb_noun or resource_action pattern. The names are readable only because of their descriptions, not because of a consistent convention.

    Tool Count5/5

    Five tools is well-scoped for a desktop automation server: observe windows, inspect a window, act, launch, and close. Each tool appears to have a distinct role in the workflow. The count is neither thin nor bloated.

    Completeness3/5

    The surface covers the core loop of listing windows, looking at one, acting on it, launching apps, and closing windows. However, window management is notably thin: close is the only explicit window operation, with no obvious focus, move, resize, minimize, or maximize operations. Agents can likely work around some gaps through act, but the window lifecycle is not fully represented.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources