Skip to main content
Glama
DanEvenSegler

Extended Playwright MCP Server

by DanEvenSegler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Extended Playwright MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Macaco Playwright by macacoai

      MCP Macaco Playwrightofficial

      macacoai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive browser automation and web interaction through Playwright with 50+ specialized functions for navigation, form filling, data extraction, and Chrome DevTools Protocol support. Designed specifically for AI agents to perform complex web workflows including scraping, testing, and automated browsing tasks.
      13 npm
      1
      Apache 2.0

    • Kryfto

      ExceptionRegret
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides 42+ MCP tools for browser automation, web scraping, and search, enabling AI agents like Claude and Cursor to browse, extract data, and run research agents on the live web.
      9
      -

    • mcp-browser

      souhailmerroun-recyclebin
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.
      -

    • jev-browser

      tontoko
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.
      7
      Apache 2.0
    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

    B3.2/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools have distinct purposes, but a few pairs overlap in function (e.g., browser_file_upload vs browser_upload_file_direct, browser_drag vs browser_drop) and could confuse an agent. Overall, descriptions help clarify the boundaries between similar actions.

    Naming Consistency4/5

    The vast majority of tools follow the browser_<action> pattern, but there are notable exceptions like `download_and_convert_images` (no browser_ prefix) and noun-style names such as browser_tabs, browser_network_requests, and browser_console_messages. These deviations are minor but break full consistency.

    Tool Count2/5

    With 46 tools, the server is heavily over-scoped for a browser automation toolkit. Many fine-grained actions like browser_key_down_up, browser_mouse_move_click, and browser_dispatch_event could be consolidated or covered by a generic evaluate tool. While the domain is broad, this count exceeds what is typically considered well-scoped.

    Completeness5/5

    The tool surface provides comprehensive coverage of browser automation: navigation, interaction, extraction, screenshots, network interception, storage management, tabs, dialogs, downloads, and geolocation. It also includes browser_run_code_unsafe to fill any remaining gaps, making the surface effectively complete for its stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources