Skip to main content
Glama
OpenMouse MCP

OpenMouse MCP

by osca5771666

Related Servers

Alternatives to OpenMouse MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to observe and control the user's live desktop by listing apps, reading accessibility trees, and performing clicks, typing, scrolling, dragging, and other input actions with per-action approvals and local audit archives.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs and agents to capture real-time, coordinate-mapped views of the full screen or a single window, including numbered interactive elements and visual diffs. It also lets them control the mouse, keyboard, clipboard, and desktop windows natively through chained multi-step actions with built-in permission toggles and failsafes.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect and operate Windows desktop applications and Chrome tabs in the background while the user retains mouse, keyboard, and window control. It provides consent prompts, hard deny lists, visible activity indicators, and an emergency stop for safer computer use.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe Windows desktop automation and computer use through natural language, including window observation, UI Automation, and execution of verified actions like clicking, typing, and scrolling.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to observe and operate real desktops, mobile devices, and browser pages through screenshots, native accessibility trees, and web automation, including clicking, typing, hotkeys, and UI lookup across macOS, Linux, Windows, Android, and iOS.
      7
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are cleanly separated: browser_open vs app_open split on URL vs executable, and the mouse_* family divides cleanly into action (move/click/drag/scroll), read (position/status), and control (stop). The only real overlap is computer_observe vs mouse_screenshot, both of which capture the active desktop/browser, though descriptions differentiate structural metadata from image capture.

    Naming Consistency4/5

    Eight of eleven tools follow a uniform resource_action pattern with the mouse_ prefix, and browser_open/app_open extend the same pattern to other resources. computer_observe is the one outlier in prefix family naming, but it remains readable and unambiguous.

    Tool Count5/5

    Eleven tools sit squarely in the well-scoped range for a desktop/browser automation server. Each mouse primitive (move, click, drag, scroll, stop, position, status, screenshot) earns its place without redundancy.

    Completeness3/5

    The pointer surface is thorough, but there is no keyboard/typing or key-press tool, which severely limits any workflow requiring text entry, form filling, or shortcuts in the browser or apps. Browser coverage also stops at opening a URL, with no navigation, tab, or element-query operations, leaving agents at dead ends for interactive pages.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues