Skip to main content
Glama
songofhawk

playwright-mcp-tabbed

by songofhawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to playwright-mcp-tabbed

No user-submitted related servers found.

    Related Servers

    • playwright-mcp-orchestrator

      mediar-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      A multi-agent orchestrator that enables multiple AI agents to share a single Chrome browser instance with tab isolation and shared state. It preserves local browser data like cookies and logins while allowing concurrent agent sessions through the official Playwright MCP.
      9
      -

    • Playwright MCP

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

    • mcp-browser-automation

      ritesh-jain
      F
      license
      B
      quality
      B
      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
      -
    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 23 tools

    Disambiguation3/5

    Most tools target distinct actions, but browser_run_code and browser_evaluate overlap heavily as JavaScript execution tools. browser_tabs bundles list/create/close tab operations while browser_context_info also describes tabs, adding some boundary ambiguity.

    Naming Consistency4/5

    The browser_ prefix is used consistently and most tools follow a verb_object style. The main deviations are noun-style names like browser_tabs, browser_context_info, browser_network_requests, and browser_console_messages, plus loose forms like browser_wait_for.

    Tool Count3/5

    23 tools is on the heavy side for an MCP server, though the browser automation scope justifies much of the surface. The count could be tightened by merging or removing the overlapping JS execution tools.

    Completeness4/5

    The toolset covers navigation, interaction, forms, uploads, drag-and-drop, dialogs, waiting, screenshots, accessibility snapshots, console logs, network requests, tabs, and browser lifecycle. Minor gaps like cookie/storage management and an explicit reload/new-page tool exist, but core automation workflows have no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources