Skip to main content
Glama

Related Servers

Alternatives to lean-browser

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through structured, token-efficient representations instead of raw accessibility trees, with navigation, element finding, form filling, screenshots, and session management. It returns a compact page orientation by default and full detail only on request, cutting context cost on content-heavy pages.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through a token-efficient, structured representation of each page rather than raw accessibility-tree dumps. Agents get compact page orientations, targeted element queries, and full interaction—clicking, typing, form filling, screenshots, and session management—while controlling how much detail is returned per call.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through structured, token-efficient representations instead of full accessibility-tree dumps, returning compact page orientations, targeted element queries, and detail on demand. Agents can navigate, click, type, fill forms, manage tabs and sessions, and inspect console or network activity at a fraction of the usual context cost.
      4 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with websites through a persistent headless Chromium session, returning compact structured page representations instead of full accessibility-tree dumps. Agents can navigate, query specific elements and forms, click, type, manage tabs and cookies, and monitor console or network activity while paying a fraction of the tokens.
      4 npm
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through compact, structured representations — landmarks, headings, forms, and typed interactive elements — rather than full accessibility-tree dumps, with three detail levels so agents pay only for the context they need. Supports navigation, targeted element queries, clicking, typing, form filling, screenshots, console/network monitoring, and multi-tab session management.
      4 npm
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to browse and interact with web pages through a typed, structured representation — receiving a compact orientation on arrival, targeted queries for specific elements, and full detail only when explicitly requested, instead of a bulky accessibility-tree dump. Supports navigation, clicking, typing, form filling, screenshots, tabs, console/network monitoring, and selectable tool profiles to cut per-call definition overhead.
      4 npm
      -

    TDQS

    C2.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct phase of browser work: open (navigate), snapshot (observe), act/fill_form (interact), extract (scrape), memory (persist), screenshot (visual capture). The main overlap is act vs fill_form, since filling a form is arguably a specialized act, and act's bundled sub-commands (tab, dialog, expect) widen its scope. Descriptions largely resolve the boundaries, so misselection risk is low but not zero.

    Naming Consistency3/5

    All names use lowercase snake_case, which is consistent at the lexical level. However, the set mixes verb-style tools (open, act, extract, fill_form) with noun-style tools (snapshot, memory, screenshot), so there is no single predictable verb_noun pattern to infer. Still readable and conventional enough for an agent to map names to behavior.

    Tool Count5/5

    Seven tools is well-scoped for a browser automation server. Each tool earns its place in a coherent workflow (navigate, observe, interact, extract, persist, visualize) with no redundant or filler tools. The count sits comfortably in the ideal 3-15 range.

    Completeness4/5

    The surface covers the core browser lifecycle: navigation, page observation, interaction, form submission, structured extraction, cross-page notes, and visual capture, with tab handling folded into act. Minor gaps exist, such as explicit history navigation (back/forward), cookie/storage management, and download handling, but these are secondary and work-aroundable via open and act.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues