Skip to main content
Glama
KitchenSink4AI

KitchenSink4Web

Official

Related Servers

Alternatives to KitchenSink4Web

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to browse and interact with web pages through compact, typed structural representations — landmarks, headings, interactive elements, and forms — served in three controllable detail levels instead of full accessibility-tree dumps. Agents can navigate, query for specific elements, fill forms, manage tabs and cookies, capture screenshots, and run audits while paying a fraction of the token cost.
      4 npm
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to automate web browsers with token-efficient perception, stealth anti-detection, captcha solving, network interception, and isolated persistent sessions.
      51
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to browse and interact with web pages through a persistent headless Chromium session, serving compact structured orientations, targeted element queries, and full detail only when explicitly requested. It supports navigation, observation, form filling, monitoring, and session management while cutting token overhead by up to ~140x versus raw accessibility-tree dumps.
      4 npm
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to browse and interact with web pages using a stealth Chromium browser, with an accessibility-tree interface for low token usage.
      12
      -

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (navigate, scroll, wait_for, monitor, manage_tabs, manage_session, get_audit, get_server_info, get_workflows), and the reading tools (get_page_view, find_elements, get_text) are carefully differentiated by purpose. However, get_page_view/find_elements/get_text all touch page content and could be confused by a less careful agent, with the descriptions doing the heavy lifting to separate them.

    Naming Consistency4/5

    Nearly all names are snake_case and follow a verb_noun pattern (manage_tabs, get_audit, get_page_view, find_elements, get_text, manage_session, get_workflows, get_server_info). A few devolve to bare verbs (navigate, scroll, monitor) or a non-verb (wait_for), but the convention is predictable overall.

    Tool Count5/5

    Twelve tools is well-scoped for a browser-automation server: navigation, reading, search, tab/session management, monitoring, waiting, and meta tools each earn a distinct place. No padding or obvious redundancy.

    Completeness3/5

    The surface covers navigation, reading, searching, tab/session lifecycle, monitoring, and meta info well, but it repeatedly promises 'refs you can act on' with no click, type/fill, screenshot, or evaluate/JS tool present. For a web-interaction server, missing the action primitives is a notable gap that would create dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues