SnapSurf
OfficialRelated Servers
Alternatives to SnapSurf
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseAqualityBmaintenanceEnables AI coding agents to open and exercise web applications in an isolated Chromium browser, capture screenshots and runtime/network diagnostics, and run deterministic page checks with linked evidence.121MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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-
- AlicenseNot gradedqualityAmaintenanceEnables agents to control a real Chromium browser with semantic tools, providing compact observations and outcome-verified actions for web interaction tasks.20 PyPI1MIT
- 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 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
Scored across 16 tools
Each tool targets a clearly distinct operation: opening vs. finding vs. acting vs. verifying vs. asserting vs. scrolling vs. reading vs. screenshotting. Descriptions consistently cross-reference the correct tool for each edge case (e.g., 'use browser_screenshot when those pixels matter', 'call browser_verify after EVERY action'), making misselection very unlikely.
Every tool follows a strict browser_<noun_or_verb> snake_case convention: browser_open, browser_find, browser_act, browser_verify, browser_assert, browser_scroll, browser_screenshot, browser_session_open, etc. No mixing of styles or inconsistent prefixes.
16 tools is slightly heavy but each earns its place within a sophisticated browser-automation surface (session lifecycle, observation, action, verification, assertion, media). No obvious redundancy; the count is justified by the depth of the domain.
Strong lifecycle coverage: sessions open/close/list, navigation, finding, acting, verification, diff/checkpoint, screenshots, text extraction, environment control. Minor gaps: no dedicated file-upload, download handling, or explicit keyboard-modifier/scroll-wheel action, but these can be worked around or are outside core scope.