cloak-auth-bridge
Related Servers
Alternatives to cloak-auth-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.149 npm2MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.-
- AlicenseCqualityAmaintenanceMCP server for agent interaction with user-approved Google Chrome tabs, enabling tab listing/control, navigation, clicking, filling, snapshots, and screenshots via a local authenticated bridge.963MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI agents faithful control of real, logged-in Chrome profiles via a secure local bridge and extension, with exact multi-profile routing and no debug profiles or remote debugging ports.6MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for local browser control via Chrome/Edge extension, enabling agents to open isolated tabs, observe pages, take screenshots, and interact with accessible controls using an existing browser profile. It is agent-agnostic, local-only, and supports safe session scoping with origin grants and sensitive-data blocking.MIT
TDQS
Scored across 9 tools
Tools cleanly separate into auth management (list_sites, sync, verify, clear) and debug session management (open, tab, list, status, close). Each tool has a distinct resource and action with no meaningful overlap or ambiguity.
Consistent use of prefixes (auth_, cloak_debug_) helps grouping, but the verb/noun pattern is mixed: most use verb_noun (cloak_debug_open, auth_verify_cloak), while a few use bare nouns (cloak_debug_status, cloak_debug_tab). The inconsistency is noticeable but not chaotic.
Nine tools is well-scoped for an auth bridge with debug capabilities. Each tool addresses a specific workflow step, and there are no redundant or filler tools.
Covers the core lifecycle for auth sync (list, sync, verify, clear) and debug session management (open, tab, list, status, close). Minor gaps remain, such as no explicit site removal or screenshot capability, but agents can achieve main workflows without dead ends.