KitchenSink4Web
OfficialRelated Servers
Alternatives to KitchenSink4Web
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT

Outcrawl MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to read web pages as clean markdown or JSON, crawl sites, search the web with results already read, monitor pages for changes, and run multi-step browser tasks under configurable limits.MIT- FlicenseNot gradedqualityAmaintenanceEnables AI agents to browse and interact with web pages through a token-efficient, structured page representation — orientation summaries, targeted element queries, and full detail only on request — instead of raw accessibility-tree dumps. Supports navigation, interaction, forms, screenshots, console and network monitoring, session/tab management, and browser-based development auditing.4 npm-
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to browse and interact with web pages through compact, structured representations — page summaries, targeted element queries, and full detail on demand — instead of paying for a full accessibility-tree dump on every call. This cuts the token cost of reading content-heavy pages by up to ~140x while still supporting navigation, forms, clicks, screenshots, and session management.4 npm-
- AlicenseNot gradedqualityAmaintenanceGives AI agents token-efficient, structured access to web pages — a compact orientation on arrival plus targeted queries for specific elements — instead of dumping the full accessibility tree on every call. Enables navigation, element interaction, form filling, screenshots, console/network monitoring, and tab and session management in a persistent headless browser.4 npmMIT
TDQS
Scored across 12 tools
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.
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.
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.
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.