Skip to main content
Glama
pm990320

ultimate-playwright-mcp

by pm990320
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ultimate-playwright-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      12 npm
      MIT

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

    • Browserose MCP

      ettomarett
      F
      license
      B
      quality
      D
      maintenance
      MCP server for AI agents to control Google Chrome via Playwright with full iframe support, enabling end-to-end browser automation including navigation, interaction within iframes, and diagnostic tools.
      24
      -
    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.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool serves a distinct browser automation action (e.g., click, type, navigate, snapshot). Potential overlaps like browser_click vs. browser_hover are clearly differentiated by operation type, and browser_evaluate handles cases outside the snapshot tree.

    Naming Consistency5/5

    All tools follow a consistent 'browser_verb_noun' pattern using snake_case. For example, browser_click, browser_navigate, browser_tab_group. No mixing of conventions.

    Tool Count5/5

    With 14 tools, the server covers core browser automation tasks without being bloated. The count feels well-scoped for its purpose.

    Completeness4/5

    The tool set covers essential browser actions (navigation, interaction, snapshot, screenshots, tabs, checkpoints). Minor gaps exist, such as no explicit scroll or file upload, but these are advanced and not critical for most automation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources