Skip to main content
Glama
Ding-Ding-Projects

lowlevel-computer-use-mcp

by Ding-Ding-Projects
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lowlevel-computer-use-mcp

No user-submitted related servers found.

    Related Servers

    • winagent

      ZYYDI1959
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI platforms to see the screen and operate any desktop software through real mouse clicks, text input, key presses, and scripted scenario execution.
      MIT

    • OmniFlow

      huppugo1
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to automate Windows desktop applications through window manipulation, image recognition, OCR, keyboard/mouse simulation, and memory operations via the MCP protocol.
      MIT

    • windows-computer-use-mcp

      KonnectSuite
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to control Windows desktop applications through UI Automation and Win32, supporting window management, mouse/keyboard input, element inspection, screenshots, OCR, macro recording, and autonomous multi-app missions. It also provides an HTTP/stdio MCP interface, an operator UI, and optional telemetry and safety controls.
      MIT

    • codex-cua-mcp

      osamabinabsar
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP agents to drive Windows applications by targeting individual windows—clicking, typing, scrolling, dragging, and reading accessibility trees or screenshots—without stealing the user's focus, mouse, or keyboard. Runs entirely locally alongside the user, with per-app approval and no cloud account or usage limits.
      MIT

    • Computer-Controller-Bridg

      Dobona
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients on Windows to control the local mouse, keyboard, and screen understanding via MCP stdio, allowing automated workflows like viewing the screen, locating elements, clicking, typing, and verifying results.
      1
      Apache 2.0
    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 59 tools

    Disambiguation3/5

    Many tools have clearly documented distinct purposes, but there is real overlap across families: background input can be done via type_text, win_send_keys, or ahk_control_send, and create_headless_desktop vs create_headless_desktops are easily confused, as are show_window/show_headless_desktop and the several list_*_windows variants. Descriptions help, but an agent must read carefully to pick the right one.

    Naming Consistency4/5

    Nearly everything is snake_case with a predictable verb_noun pattern (list_windows, move_window, kill_process, wsl_run). Minor deviations exist: some noun-first status tools (window_action, startup_status, is_admin) and three different input-naming families (type_text vs win_send_keys vs ahk_control_send), but casing and readability stay consistent.

    Tool Count2/5

    59 tools is heavy and well into the over-scoped range. The domain is genuinely broad (Windows GUI input, headless desktops, Linux Xvfb, WSL, recording, admin), which justifies more than average, but the count still imposes high selection costs and several tools are thin parallels of each other.

    Completeness4/5

    Coverage is extensive and lifecycle-aware: create/launch/list/close for headless desktops and virtual displays, create/run/list/destroy for WSL, plus full input, window, process, file, screenshot, and recording surfaces. Only minor gaps (e.g. clipboard access, richer window attribute queries) keep it from a 5.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources