Skip to main content
Glama

Related Servers

Alternatives to jevnav

  • A
    license
    A
    quality
    F
    maintenance
    Stateful 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,309 npm
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides complete browser automation capabilities for AI agents via 44 tools, including navigation, element interaction, state management, and session recording.
    85 npm
    1
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables 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.
    195 npm
    7
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables 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.
    10 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables browser automation where a calling LLM states one desired outcome per step and a separate decision model chooses the element, action, value, and completion status, with Playwright carrying out the action. Exposes tools for navigating, performing and verifying steps, reading question-relevant page text, taking snapshots, capturing screenshots, and invoking tools that pages register for agents.
    889 npm
    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

ActivityNo data
ResponsivenessSyncing