SnapSurf
OfficialRelated Servers
Alternatives to SnapSurf
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables agents to control a real Chromium browser with semantic tools, providing compact observations and outcome-verified actions for web interaction tasks.1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to rapidly drive and inspect real web pages through persistent browser sessions, using accessibility-tree snapshots and DevTools-grade diagnostics to identify and diagnose issues.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to verify application changes by running browser workflows, executing independent state assertions, and producing replayable evidence.1 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform end-to-end web testing by controlling a real browser through tools for navigation, interaction, state inspection, screenshots, and script evaluation.MIT
- AlicenseAqualityAmaintenanceGives AI agents a compact, semantic interface to the browser, returning structured page snapshots with stable element IDs instead of raw DOM. Enables agents to navigate, interact, and extract information from web pages efficiently.626353 npm17MIT
- AlicenseCqualityAmaintenanceEnables 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.315MIT
TDQS
Scored across 16 tools
Every tool targets a distinct operation—navigation, acting, verification, diffing, searching, reading, viewing, scrolling, and session management—so an agent can reliably pick the right one. Even the diff-related tools (browser_verify and browser_diff) are cleanly separated by their baselines: post-action vs checkpoint.
All tools share the browser_ prefix and snake_case, with a mostly verb-first pattern (open, act, find, scroll, verify, assert). A few names are noun-like (browser_text, browser_page, browser_environment, browser_parent), but the overall convention remains predictable and readable.
At 16 tools, the set sits just above the ideal 3–15 range, but each tool carries real weight for a browser automation server. The count feels justified by the breadth of navigation, observation, interaction, verification, and session management responsibilities.
The core browse → observe → act → verify → assert loop is fully supported, including sessions, environments, and diff-based assertions. Minor gaps like explicit back/forward navigation or direct cookie APIs are absent, but these are workaroundable and do not break typical workflows.