Skip to main content
Glama
91fapiao-cn

playwright-browser-skill

by 91fapiao-cn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to playwright-browser-skill

No user-submitted related servers found.

    Related Servers

    • mcp-browser-automation

      ritesh-jain
      F
      license
      B
      quality
      D
      maintenance
      An MCP server for generic browser automation using Playwright. Enables MCP clients to navigate pages, inspect elements, execute JavaScript, capture screenshots, and monitor console logs and network traffic via a headless Chromium instance.
      7
      -

    • 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.
      8 npm
      1
      MIT

    • 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

    • Playwright Plus Python MCP

      MCP-Mirror
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables browser automation and web scraping through Playwright, supporting navigation, screenshots, element interaction, form filling, JavaScript execution, and content extraction.
      8
      Apache 2.0

    • Browser MCP Server

      Akioo77
      A
      license
      A
      quality
      C
      maintenance
      A browser automation tool using Playwright and MCP protocol, enabling agents like OpenClaw or Claude Desktop to control a browser for navigation, content extraction, and interaction.
      21
      5 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

    C2.2/5.0

    Scored across 101 tools

    Disambiguation2/5

    Many tools have overlapping boundaries despite prefix clarity: browser_click vs browser_mouse_click, browser_tap vs browser_touchscreen_tap, and browser_fill vs browser_type vs browser_keyboard_insert_text are easy to confuse. The get_by_* family also creates a large group of highly similar tools where an agent may struggle to pick the right one.

    Naming Consistency4/5

    The browser_ prefix and snake_case naming is consistent, and most tools follow a browser_verb_noun pattern. Minor deviations like browser_goto, browser_pdf, browser_count, and browser_get_coverage (which actually starts coverage) keep it from being perfectly uniform.

    Tool Count1/5

    At 101 tools, this is an extreme count that will overwhelm agent context and selection. Even for broad browser automation, many tools could be consolidated (e.g., wait_for_* variants, get_by_* variants, mouse/keyboard actions), so the surface is far larger than necessary.

    Completeness5/5

    The tool surface is exceptionally comprehensive for browser automation, covering browser lifecycle, navigation, interactions, queries, waits, screenshots, network control, storage, permissions, clocks, and accessibility. There are no obvious dead ends or major missing capabilities for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources