Skip to main content
Glama
Winds-AI

autonomous-frontend-browser-tools

by Winds-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to autonomous-frontend-browser-tools

No user-submitted related servers found.

    Related Servers

    • MCP Browser Use Server

      JovaniPink
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with web browsers using natural language, featuring automated browsing, form filling, vision-based element detection, and structured JSON responses for systematic browser control.
      62
      MIT

    • Cloudflare Playwright MCP

      q275212
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Cloudflare Playwright MCP

      AI24K
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Cloudflare Playwright MCP

      xvv6u577
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Safari MCP Server

      lxman
      A
      license
      B
      quality
      D
      maintenance
      Provides AI assistants with Safari browser automation and developer tools access, enabling LLMs to control Safari, access console logs, monitor network activity, and perform browser automation tasks.
      13
      9 npm
      33
      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 9 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists. For example, 'browser.console.read' and 'browser.network.inspect' both handle error debugging, though they focus on console logs versus network requests respectively. The 'api.request' and 'api.searchEndpoints' tools are clearly differentiated, with one for execution and one for discovery.

    Naming Consistency5/5

    Tool names follow a consistent dot-separated pattern (e.g., 'api.listTags', 'browser.navigate', 'ui.inspectElement'), using clear verb_noun structures. This predictability makes it easy for agents to understand the tool's domain and action at a glance, with no mixing of conventions.

    Tool Count5/5

    With 9 tools, the set is well-scoped for autonomous frontend browser testing and debugging. It covers key areas like API interaction, browser navigation, network inspection, UI debugging, and interaction, providing a comprehensive toolkit without being overwhelming or sparse.

    Completeness4/5

    The toolset offers strong coverage for frontend automation, including API testing, browser navigation, debugging, and UI interaction. A minor gap exists in direct browser storage management or cookie handling, but core workflows like debugging, navigation, and interaction are well-supported.

    Resources