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
673 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.4027 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.522 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides complete browser automation capabilities for AI agents via 44 tools, including navigation, element interaction, state management, and session recording.393 npm1Apache 2.0
- 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.1,206 npm1MIT
- 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.MIT
- 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
- AlicenseAqualityBmaintenanceEnables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.2MIT
TDQS
A3.8/5.0
Scored across 33 tools
Disambiguation4/5
Most tools target clearly distinct concerns: navigation, state inspection, form filling, network, dialogs, tracing, and tab management. A few adjacent pairs (browse vs. goal, page_state vs. outline) could be confused at a glance, but the descriptions define their boundaries well.
Naming Consistency4/5
Names are all lowercase, readable, and mostly follow a verb_noun or imperative style (upload_files, fill_form, trace_start, select_page). The mix of noun-only names like network, dialogs, tabs, and summary is a minor deviation rather than a real inconsistency.
Tool Count2/5
At 33 tools, the surface exceeds the 25+ threshold that typically reads as too many for one server. Each tool appears individually purposeful, but the count is heavy for an agent to consider reliably, and several debugging/performance tools could plausibly be consolidated.
Completeness4/5
The set covers navigation, tab management, state inspection, form interaction, waiting, dialogs, network stubbing, tracing, and high-level goal execution—a broad and mostly complete browser-automation surface. Obvious gaps include no explicit selector-based click tool, no back/forward navigation, and no cookie or storage management.
Maintenance
ActivityMaintained
ResponsivenessNo issues