Skip to main content
Glama

Related Servers

Alternatives to moonlighting-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive a real headful Chrome browser using vision-first computer interactions, with support for multi-agent tab groups, password-manager-filled logins, and human handoff.
      4 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Drives your real local Chrome with profile isolation, allowing LLMs to interact with your logged-in sessions without modifying your actual profile.
      13
      16 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to navigate, inspect, and interact with real websites via a persistent headless Chromium session, returning compact structured orientations, targeted element queries, and full detail only on request rather than dumping raw accessibility trees. This cuts token usage by roughly 10–140x on content-heavy pages while still supporting clicking, typing, form filling, screenshots, dialog handling, and multi-tab sessions.
      4 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding agents to work inside a disposable Windows guest desktop, where they can run shell commands, launch applications, inspect and operate native GUI controls, perform browser DOM actions, and transfer files. Fresh observations, PNG screenshots, and hashed artifacts let agents verify results without touching the host desktop.
      18
      MIT

    TDQS

    B3.2/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools map to a distinct browser action (navigate, click, type, hover, drag, screenshot), and paired tools like browser_network_requests/browser_network_request and browser_snapshot/browser_find are clearly differentiated by description. However, some boundaries blur: browser_evaluate vs browser_run_code_unsafe both execute JS, and browser_drop vs browser_drag both involve drag semantics, which could cause occasional misselection.

    Naming Consistency4/5

    Names follow a consistent snake_case browser_<verb|noun> pattern (browser_navigate, browser_click, browser_take_screenshot, browser_network_requests) with predictable prefixes. The only deviation is the two cred_* tools, which use a different domain prefix but still keep the same verb_noun style, so it remains readable.

    Tool Count3/5

    At 27 tools the set sits above the 25-tool 'heavy' threshold, and a few pairs (network_requests/network_request, evaluate/run_code_unsafe) could be consolidated. Still, browser automation is a genuinely broad domain where most tools earn their place, so it is heavy rather than bloated.

    Completeness4/5

    The surface covers the full browser lifecycle: navigation, element interaction, forms, tabs, dialogs, file upload, network/console inspection, snapshots, screenshots, media emulation, and credential filling. Minor gaps exist (no explicit cookie/storage-state management or download handling), but core workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues