Skip to main content
Glama
unilab-hq

aiwebhelper

by unilab-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to aiwebhelper

No user-submitted related servers found.

    Related Servers

    • Ghostlight

      sylin-org
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.
      25
      1
      Apache 2.0

    • Echo

      krishngohel
      A
      license
      Not graded
      quality
      A
      maintenance
      Local browser MCP server that lets AI assistants control a real desktop browser via tools like navigate, snapshot, and search_web.
      MIT

    • huashu-chrome

      alchaincyf
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP-compatible AI agent to drive your own Chrome browser with your existing login state, filling forms, clicking elements, fetching data, and handling captchas without API keys or re-authentication.
      710 npm
      205
      MIT

    • chrome-control-mcp

      RandyNorthrup
      A
      license
      Not graded
      quality
      A
      maintenance
      A native MCP server that gives AI assistants full Chrome control via the DevTools Protocol and an unpacked extension, including semantic element refs, real input, screenshots, and browser/tab/window management. It exposes 43 callable tools with a visible control overlay and an optional read-only security profile.
      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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    The tools split cleanly into pick management, page interaction, and onboarding. The pick tools each have a distinct behavior — waiting, returning latest, listing, clearing — and the page_* tools are distinct interaction actions, so agents should be able to choose the right one.

    Naming Consistency3/5

    The page_* tools follow a clear, consistent verb pattern, but the pick-related tools are inconsistent: latest_pick, list_picks, clear_picks, and wait_for_pick mix singular/plural and different phrase structures. how_to_start is also a one-off, making overall naming mixed but still readable.

    Tool Count5/5

    With 13 tools, the server is well-scoped for its purpose. The tools cover onboarding, pick lifecycle, tab awareness, page reading, interaction, and a JavaScript escape hatch without feeling bloated or redundant.

    Completeness5/5

    The tool set covers the full assisted-browsing workflow: setup, picking, waiting, page introspection, navigation, clicking, typing, pointing out, and arbitrary JavaScript for unusual cases. The page_run tool especially fills any long-tail gaps that the more specialized tools cannot handle.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources