A
licenseA
qualityF
maintenanceStateful MCP server wrapping Playwright for browser automation. Provides tools to navigate, interact, and extract data from web pages via a persistent browser session.
19
1,212 npm
MIT
jevnav
by dtduc-git
Related Servers
Alternatives to jevnav
- AlicenseAqualityCmaintenanceEnables AI agents to fully control a browser for web automation, including navigation, clicking, typing, scrolling, screenshots, and DOM inspection, with session persistence and anti-bot bypass.4019 npmMIT
Related Servers
- AlicenseAqualityDmaintenanceProvides an LLM with a real Chromium browser to perform web tasks, recording every action into a structured trace for later verification of goal completion.528 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides complete browser automation capabilities for AI agents via 44 tools, including navigation, element interaction, state management, and session recording.81 npm1Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents to open and exercise web applications in an isolated Chromium browser, capture screenshots and runtime/network diagnostics, and run deterministic page checks with linked evidence.121MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a real Chrome browser for autonomous web tasks, using fast typed decisions with calibrated confidence, human-in-the-loop questions, safety gates, and full debug traces.447 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a real browser through intent-based tools—reading pages, filling forms, clicking, and replaying self-healing recipes—while returning only concise answers instead of the DOM.8 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform end-to-end web testing by controlling a real browser through tools for navigation, interaction, state inspection, screenshots, and script evaluation.MIT
TDQS
A3.7/5.0
Scored across 33 tools
Disambiguation4/5
Most tools have distinct purposes and detailed descriptions that clarify boundaries (e.g., page_state vs outline vs styles, browse vs goal). A few adjacent tools like wait_for/page_state and the many diagnostic tools could still be confused, but the set is largely unambiguous.
Naming Consistency3/5
All names use snake_case, but conventions are mixed: action verbs (goto, scroll, press_key), noun-like observation tools (page_state, console, network), and noun_verb pairs (trace_start/trace_stop). Readable but not a consistent verb_noun pattern.
Tool Count2/5
33 tools is too many for the apparent scope. While browser automation is broad, many advanced diagnostic tools (perf_metrics, heap_snapshot, lighthouse, trace_start/stop, network_detail) could be consolidated or made optional, making the surface heavy.
Completeness4/5
Core browser automation is well-covered: navigation, element interaction, forms, tabs, network/dialog observation and interception, emulation, and performance/tracing. Minor gaps exist (e.g., explicit hover/double-click, cookie/storage, iframe handling) but agents can often work around them.
Maintenance
ActivityMaintained
ResponsivenessNo issues