Skip to main content
Glama
cuber-it

mcp-playwright-tools

by cuber-it
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-playwright-tools

No user-submitted related servers found.

    Related Servers

    • agentic-browser-mcp

      q35888
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to automate a real Chrome browser via Playwright, supporting session sharing and tools for navigation, clicking, typing, and more.
      11
      2
      MIT

    • OpenBrowser

      SangoAlgo
      A
      license
      Not graded
      quality
      C
      maintenance
      An enhanced MCP Playwright browser server that enables robust web automation with persistent locator caching, multi-level click fallbacks, accessibility tree interactions, and smart handling of navigation and popups.
      302 npm
      MIT

    • browser-mcp-lab

      ashu0729will
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables browser automation through MCP, providing tools for navigation, interaction, page inspection, and form handling via a pinned Playwright MCP server.
      1
      MIT

    • InSite

      jowharshamshiri
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive browser automation MCP server using Playwright, offering 50+ tools for page control, element interaction, content extraction, and more across multiple browser engines.
      13 npm
      1
      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

    C2.8/5.0

    Scored across 73 tools

    Disambiguation4/5

    Tools are mostly distinct with clear descriptions, but there are multiple variants for clicks (click, click_by_role, click_by_text, double_click, right_click) and finds (find_by_label, find_by_placeholder, etc.) which could cause confusion if descriptions are not read carefully.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun or verb_preposition_noun pattern with lowercase and underscores. Even single-word verbs (e.g., click, fill) are uniform. The naming is predictable and clear.

    Tool Count2/5

    With 73 tools, the count far exceeds the typical scope for a tool server. While browser automation is complex, many tools could be consolidated (e.g., merging click variants). This volume risks overwhelming agents.

    Completeness4/5

    The set covers a broad range of browser automation tasks: navigation, form interaction, waiting, cookies, storage, frames, dialogs, and recording. Minor gaps exist (e.g., no device emulation or performance metrics), but core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources