Skip to main content
Glama
krw82

jev-playwright-mcp

by krw82
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jev-playwright-mcp

No user-submitted related servers found.

    Related Servers

    • gaze

      KevinTrinhDev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a real, already logged-in browser from the CLI or over MCP, with enforceable approval gates for actions and safeguards against prompt injection.
      1,795,674 npm
      1
      Mozilla Public 2.0
    • AgentWall by agentwall

      AgentWallofficial

      agentwall
      A
      license
      Not graded
      quality
      C
      maintenance
      Policy-enforcing MCP proxy that blocks dangerous tool calls before they execute. Protects credentials, filesystem, shell, and databases across Claude Desktop, Cursor, Windsurf, and OpenClaw.
      5 npm
      39
      Apache 2.0

    • browser-guard-mcp

      egoring
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to automate browsers through Playwright behind multi-layer safety guards, restricting navigation to allowed domains, defaulting to read-only actions, and recording all behavior in audit logs.
      7
      MIT

    • nexus-browser-mcp

      paipaipai666
      A
      license
      B
      quality
      B
      maintenance
      A browser-automation MCP server built on Playwright that provides deterministic snapshots via MutationObserver/requestAnimationFrame, HITL governance, multi-task isolation, and self-healing browser sessions for LLM-driven browsing.
      25
      22 PyPI
      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

    B3.1/5.0

    Scored across 28 tools

    Disambiguation4/5

    Each tool targets a different browser capability, and pairs like browser_network_requests/browser_network_request or browser_snapshot/browser_find are clearly complementary. The only mild ambiguities are browser_type vs browser_fill_form and browser_drag vs browser_drop, but the descriptions are enough to disambiguate them.

    Naming Consistency4/5

    Names consistently start with browser_ and are lowercase snake_case, and most follow a verb-first pattern like navigate, click, take_screenshot, and select_option. A handful of resource-style names such as tabs, network_requests, console_messages, snapshot, and jev_status break the verb_noun pattern, but the shared prefix keeps the set predictable.

    Tool Count2/5

    28 tools exceeds the 25-tool threshold and feels heavy, especially with granular near-duplicate primitives such as drag/drop, type/fill_form, and snapshot/find plus JEV/WebMCP-specific tools. Some tools earn their place, but the surface could be consolidated without much loss.

    Completeness4/5

    The surface covers the core browser automation lifecycle: navigation, interaction, forms, uploads, waits, snapshots, console/network inspection, and tab/page management. Minor gaps like reload/forward, cookie/localStorage management, and download handling can be worked around via browser_evaluate or browser_run_code_unsafe.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources