Skip to main content
Glama
mlnima

browser-use-native-windows

by mlnima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to browser-use-native-windows

No user-submitted related servers found.

    Related Servers

    • pc-bot

      ChristopherDond
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Windows by clicking, typing, and navigating with a visible cursor overlay, using a layered approach (native UIA, browser CDP, pixel fallback) for reliable interaction.
      1
      -

    • agent-browser-mcp

      LinVireo
      A
      license
      B
      quality
      A
      maintenance
      MCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.
      55
      2
      MIT

    • computer-use-windows

      wimi321
      A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for Windows desktop control, enabling screenshots, mouse and keyboard input, app launch, window/display management, and clipboard access via natural language.
      2
      MIT

    • pc-control-agent

      anbu-20012005
      F
      license
      Not graded
      quality
      C
      maintenance
      This MCP server enables an AI agent to control a Windows PC through human-like interactions such as screen capture, OCR, mouse, keyboard, and navigation, without using shortcut APIs.
      -

    • windows-computer-use-mcp

      Einosensokami
      A
      license
      Not graded
      quality
      C
      maintenance
      A local, dependency-free MCP server that gives AI agents controlled access to the active Windows desktop, enabling automated interaction with applications through screenshots, clicks, typing, and window management.
      54
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: browser_observe for launching/adopting and getting observation, browser_act for performing actions, browser_status for checking state, and browser_stop for cleanup. No overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent 'browser_' prefix followed by a single verb (observe, act, status, stop), all lowercase, with no mixing of conventions.

    Tool Count5/5

    Four tools is exactly right for this domain: observe, act, status, and stop cover the essential lifecycle without unnecessary extras. Not too few, not too many.

    Completeness5/5

    The tool set covers the full lifecycle of native browser interaction: initialization (browser_observe), action (browser_act), monitoring (browser_status), and termination (browser_stop). No obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources