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

    • 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

    • atomic-computer-mcp

      Dawdler-G
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables automation of native Windows desktop applications through screen capture, mouse/keyboard control, and waiting for UI changes, exposing them as MCP tools.
      1
      -

    • Computer Use MCP

      A8Cl233395
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to observe and control Windows desktop applications by reading UIA element trees and capturing screenshots, then acting through UIA patterns or synthesized mouse and keyboard input. It runs standalone on an interactive Windows session, without requiring the original host application.
      -
    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.6/5.0

    Scored across 58 tools

    Disambiguation4/5

    Despite the large catalog, each tool targets a distinct resource or action: mouse actions, window controls, screen recording lifecycle, WSL temp distros, and admin/startup tasks are each fairly separable. A few near-neighbors—create_headless_desktop vs create_headless_desktops and the several text/keystroke senders—require close reading of descriptions but are ultimately distinguishable.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern such as get_cursor_position, list_windows, launch_on_virtual_display, and wsl_destroy. Minor inconsistencies like window_action (noun_noun), win_send_keys (prefix_verb_noun), and status-only names like ahk_status or linux_status break the otherwise predictable convention.

    Tool Count2/5

    58 tools is far above the well-scoped range and will impose a heavy selection burden on an agent even though the tools are logically grouped into subsystems. The raw number is excessive for a single MCP server, especially with many status/inspection helpers that could be consolidated.

    Completeness4/5

    The surface covers mouse and keyboard input, window and control automation, process management, file transfer, screen capture/recording, headless desktops, WSL, AHK, and startup lifecycle, leaving few hard dead ends. Minor gaps exist—no dedicated Linux virtual-display input tool and no clipboard/OCR helper—but these can often be worked around via run_command.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources