sessfork-browser
Related Servers
Alternatives to sessfork-browser
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to access authenticated websites by reusing your existing browser profile and cookies, so you never share passwords and sessions persist between runs.55MIT
- AlicenseNot gradedqualityCmaintenanceEnables an agent to drive a persistent Chrome window you stay logged into, so its browsing uses your existing sessions and cookies. It deliberately avoids stealing window focus when tabs are opened or switched, letting you keep working elsewhere while the agent operates.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control and inspect the user's actual Chrome browser via MCP, preserving login sessions and isolating agent tasks in background tab groups without disrupting the user's workflow.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to drive your real, logged-in Chrome browser with existing sessions and cookies, bypassing CAPTCHA and anti-bot measures, with support for multi-session and human-in-the-loop workflows.4066MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to securely control a user's existing signed-in Chrome browser through isolated tab groups, with strict per-session ownership and no cookie or token exposure.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a user's real Chrome browser tabs, executing JavaScript, reading cookies, and making fetch requests within authenticated sessions.-
TDQS
Scored across 25 tools
Each tool maps to a fairly distinct browser action, and the descriptions actively disambiguate tricky pairs (snapshot vs screenshot, find vs snapshot, network_requests vs network_request). Minor overlap remains between browser_run_code_unsafe and the specialized tools, and between browser_type/browser_fill_form, but the guidance is clear enough to choose correctly.
Every tool uses the same browser_<snake_case_action> convention with predictable verb or noun phrasing. The singular/plural pair browser_network_requests and browser_network_request is intentional and documented, not an inconsistency.
25 tools is at the heavy end for the stated scope; while browser automation is inherently broad, several low-frequency capabilities (drop, emulate_media, resize, run_code_unsafe) push the surface toward the ceiling. It is workable but feels padded rather than tightly scoped.
Core lifecycle coverage is strong: navigation, interaction, forms, tabs, network, console, screenshots, and dialogs are all present. Gaps are minor but real — no forward navigation counterpart to browser_navigate_back, and no explicit cookie/storage or download handling, though browser_evaluate and browser_run_code_unsafe can work around these.