Playwright JEV
Related Servers
Alternatives to Playwright JEV
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to browse and interact with web pages through a persistent headless Chromium session, serving compact structured orientations, targeted element queries, and full detail only when explicitly requested. It supports navigation, observation, form filling, monitoring, and session management while cutting token overhead by up to ~140x versus raw accessibility-tree dumps.4 npm-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to browse the web through a persistent headless Chromium session that returns compact, structured page summaries and targeted queries instead of full accessibility-tree dumps. Agents can navigate, observe, search, and interact with pages using configurable detail levels and tool profiles, cutting token costs by up to ~140x on content-heavy sites.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to drive a real Chromium browser by receiving compact, token-efficient page maps and only the changes after each action. It guards against hidden prompt injections, blocks payments, sends and deletions until the user approves, and lets agents learn site-specific notes over time.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to automate a live Chrome browser with compact DOM serialization, authenticated session continuity, and human-like input trajectories.6 npmMIT
- AlicenseBqualityCmaintenanceEnables LLM agents to automate web browsers with token-efficient perception, stealth anti-detection, captcha solving, network interception, and isolated persistent sessions.51MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to automate browsers and interact with web pages using structured accessibility snapshots rather than screenshots or vision models.Apache 2.0
TDQS
Scored across 25 tools
Most tools target distinct browser actions (click, hover, type, navigate, snapshot, screenshot). A few pairs overlap somewhat — browser_drop vs browser_drag, and browser_evaluate vs browser_run_code_unsafe — but descriptions clarify their boundaries well enough to select correctly.
Every tool uses the browser_ prefix with consistent snake_case verb/noun phrasing (browser_navigate, browser_take_screenshot, browser_select_option). The pattern is uniform and predictable across all 25 tools.
25 tools is on the heavy side, but browser automation is a genuinely broad domain and nearly every tool covers a distinct capability (dialogs, network, console, tabs, media emulation). Slightly over-scoped but each tool earns its place.
The surface covers the full interaction lifecycle: navigation, interaction, forms, dialogs, file upload, network/console inspection, and screenshots. Minor gaps like explicit cookie/localStorage management exist, but agents can work around them via browser_evaluate.