jev-playwright-mcp
Related Servers
Alternatives to jev-playwright-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely control a browser through MCP by enforcing deterministic policies, keeping secrets out of model context, and requiring human confirmation for risky actions.Apache 2.0- AlicenseNot gradedqualityBmaintenanceAn MCP policy proxy that sits between AI agents and their upstream MCP servers to enforce hard spend and blast-radius caps, human approvals for destructive tools, a kill switch, scoped per-agent credentials, dry-run writes with mutation diffs, semantic loop breaking, and a hash-chained audit log. It also offers hook mode that applies the same policy to coding agents' own shell commands and file edits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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,133,569 npmMozilla Public 2.0
- AlicenseNot gradedqualityAmaintenanceEnables LLM agents to automate a Playwright browser by specifying natural-language outcomes and candidate values while a decision model selects elements, actions, and completion status. Exposes MCP tools for navigation, goal execution, page checking/reading, snapshots, screenshots, direct actions, and invoking page-provided WebMCP tools.0MIT
- FlicenseBqualityDmaintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.101-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Claude Code and IDE agents to call a tool that drives a real Playwright browser to complete web tasks, with sensitive actions automatically refused when no human is available to approve them.MIT
TDQS
Scored across 28 tools
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.
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.
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.
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.