Skip to main content
Glama

Related Servers

Alternatives to Browser MCP

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to navigate and interact with web pages through compressed semantic graphs, using element IDs and coordinates for clicking, typing, selecting, scrolling, and screenshots without raw HTML or CSS selectors.
    39 npm
    1
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Converts raw HTML into structured, AI-readable page maps with 97% token reduction, enabling agents to read, click, type, and navigate any web page.
    9
    13
    36
    AGPL 3.0
  • A
    license
    C
    quality
    A
    maintenance
    Enables AI agents to automate real Chrome via a structured Semantic Action Graph, without screenshots, CDP, or bot detection. It supports clicks, form filling, navigation, and state diffs on strict-CSP sites and modern SPAs.
    31
    5
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI agents to understand web page structure and content through structured data extraction and element discovery using Playwright, eliminating the need for screenshots.
    4
    7 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Reachability-filtered browser perception and actions for AI agents. Filters snapshots to elements a user could actually reach (removes modal-occluded, closed-drawer, off-screen and inert elements), with ref-stable snapshots and state diffs.
    1
    Apache 2.0
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to perceive and interact with web interfaces by extracting a unified UI Scene Graph from live URLs, providing tools for navigation, element detection, visual analysis, and state tracking.
    1
    -

TDQS

A3.9/5.0

Scored across 26 tools

Disambiguation5/5

Each tool has a clearly distinct purpose, from navigation (navigate, go_back) to element interaction (click, hover, drag) to form handling (get_form, type). There is no overlap between tools; even similar operations like scroll and wheel are differentiated by mechanism.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern, using snake_case for multi-word names (e.g., close_page, list_pages, scroll_to). Single-word verbs (click, drag, hover) are also consistent. No mixing of conventions.

Tool Count4/5

With 26 tools covering navigation, interaction, form handling, network inspection, and canvas analysis, the count is slightly high but justified for a comprehensive browser automation server. Each tool serves a specific need, though a few might be consolidated.

Completeness3/5

The tool set covers most common browser automation tasks, but notable gaps exist: no explicit wait_for_element or wait_for_navigation, no JavaScript execution, and no cookie management. These omissions may require workarounds for certain scenarios.

Maintenance

ActivityMaintained
ResponsivenessSlow