Skip to main content
Glama
jett666-rx

fast-gui

by jett666-rx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to fast-gui

No user-submitted related servers found.

    Related Servers

    • newton-browser

      Koala-Studios
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.
      MIT

    • agent-browser-mcp

      LinVireo
      A
      license
      A
      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.
      51
      46 PyPI
      1
      MIT

    • browser-store

      bysking
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
      3 npm
      MIT

    • browser-bridge

      jeffkit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote agents to control a local Chrome/Edge browser via MCP, supporting navigation, snapshots, clicks, typing, screenshots, and script execution.
      14 npm
      ISC

    • Real Browser MCP

      ton-to-ton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
      73 npm
      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

    B3.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    The toolset mostly maps each tool to a distinct capability: navigation, observation, action, verification, capture, and page lifecycle are separated. However, `open_click_verify` and `act` can both be used for clicking, and `open_url`'s optional table/ref returns overlap with `extract_tables`, creating two possible mis-selection points despite helpful descriptions.

    Naming Consistency3/5

    Most tools follow an imperative verb + object snake_case pattern (`list_targets`, `close_target`, `open_url`, `extract_tables`, `wait_for`, `verify`). The pattern is weakened by noun-style names (`capabilities`, `price_radar`, `external_model_plan`) and the compound multi-verb `open_click_verify`, so consistency is only moderate.

    Tool Count4/5

    14 tools is a reasonable scope for a browser/GUI automation server and stays within the comfortable range. The count would be ideal if not for a couple of peripheral tools (`price_radar`, `external_model_plan`) that sit outside the core automation loop.

    Completeness4/5

    The core GUI automation lifecycle is well covered: open, observe, act (single and batch), wait/verify, capture, close, list targets, and safety introspection are all present. Minor gaps include the lack of a standalone input/typing tool and no explicit target reconciliation action, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources