Skip to main content
Glama
dgutierrez1

concurrent-playwright-mcp

by dgutierrez1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to concurrent-playwright-mcp

No user-submitted related servers found.

    Related Servers

    • Playwright MCP

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright.
      5,425,474 npm
      Apache 2.0

    • 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
      -

    • playwright-mcp-tabbed

      songofhawk
      A
      license
      B
      quality
      D
      maintenance
      A tab-aware Playwright MCP server that enables multiple agents to operate on different tabs concurrently while sharing a single browser context and login session.
      23
      6 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

    A3.5/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a specific browser automation action (click, type, navigate, etc.) with clear boundaries. The only potential overlap is between browser_type and browser_fill_form, but the latter is explicitly for multiple fields, so no confusion.

    Naming Consistency5/5

    All tools follow the exact same `browser_<verb>` pattern in snake_case, providing a predictable and intuitive naming scheme. There are no deviations or mixed conventions.

    Tool Count4/5

    At 23 tools, the set is comprehensive but on the higher side. However, each tool serves a distinct and necessary browser automation function, so the count is justified and not excessive.

    Completeness4/5

    The tool surface covers nearly all essential browser automation tasks: navigation, interaction, evaluation, dialogs, network, console, sessions, storage, tabs, waiting, and screenshots. Minor gaps like scrolling or raw DOM queries exist but are workable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources