session-broker
Related Servers
Alternatives to session-broker
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to reuse a human-completed Chrome login session to open confirmed origins, read visible page text, and perform single click, fill, or key press actions without ever handling passwords or exposing cookies.6MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to authenticate with websites using a real Chromium browser with anti-detection measures and human-in-the-loop support for captchas and 2FA. Features stealth browsing, human-like interactions, and persistent session storage to automate and resume login workflows.-
- AlicenseAqualityBmaintenanceEnables 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 agents to drive a headless Chrome browser that is already logged in to the user's accounts, supporting multiple accounts and safe handling of Google sessions without manual login or 2FA.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.4060MIT
- AlicenseBqualityAmaintenanceGives agents an autonomous browser that takes a single goal-level call and drives a real Chrome step by step, returning a verified result or a concrete question instead of guessing. It keeps passwords out of prompts, requires approval before buy/pay/delete actions, and detects login walls and bot challenges.98 npm2MIT
TDQS
Scored across 5 tools
Each tool has a distinct role in the session lifecycle: browsing, listing, deleting, starting login, and completing login. The two-phase sign_in/complete_sign_in flow is clearly separated and not ambiguous.
Most tools follow a clear imperative verb_noun or phrasal-verb pattern like list_sessions, complete_sign_in, and sign_in. Browse and revoke are less descriptive but still readable and not confusing.
Five tools is well-scoped for a session-broker service. Each tool covers a necessary part of the workflow without redundancy.
The tool surface covers the full lifecycle: create a session (sign_in/complete_sign_in), use it (browse), inspect it (list_sessions), and destroy it (revoke). No obvious gaps exist for the stated purpose.