SoftGlaze Browser MCP
Related Servers
Alternatives to SoftGlaze Browser MCP
- AlicenseBqualityCmaintenanceA stdio helper that connects AI apps to the local SoftGlaze Browser MCP server, relaying token-scoped tool, prompt, and resource requests while requiring approval in the browser app.39MIT
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to control Multilogin X anti-detect browser profiles via a streamable HTTP MCP interface. Supports profile management, session handling, and a broad catalog of browser actions such as navigation, clicking, typing, screenshots, and more.-
- AlicenseNot gradedqualityBmaintenanceConnects AI agents to an existing Chromium browser profile through a local background service and extension, exposing browser control over MCP stdio. It lets agents navigate tabs, capture accessibility snapshots and screenshots, click, fill forms, type, scroll, drag, and run raw CDP commands, with multiple browser profiles selectable by ID.5 npmDo What The F*ck You Want To Public
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser server so they can navigate, interact with, and extract content from web pages without getting blocked. Provides 47 tools spanning tabs, navigation, interaction, observation, search, sessions, profiles, downloads, extraction, presets, and batch workflows.899 npmMIT

GoLogin MCPofficial
AlicenseCqualityCmaintenanceManage your GoLogin browser profiles and automation directly through AI conversations. This MCP server connects to the GoLogin API, letting you create, configure, and control browser profiles using natural language.59142 npm24MIT- FlicenseNot gradedqualityAmaintenanceExposes a localhost MCP endpoint that lets AI agents drive isolated browser profiles — navigating, clicking, typing, extracting, screenshotting, evaluating JS, and managing tabs and cookies — so real authenticated workflows can be completed from MCP clients like Cursor or Claude Desktop. Cookies, login state, fingerprints, and proxies persist per profile across launches and AI sessions.-
- AlicenseCqualityDmaintenanceMCP server for HotLogin Local API that enables AI agents to manage browser environments, groups, and proxies, and perform browser automation tasks like page interaction and cookie management through a standardized interface.23250 npmMIT
TDQS
Scored across 39 tools
Most tools have clearly distinct resource+action targets (page_click vs page_type vs page_scroll, create_profile vs update_profile vs assign_proxy). A few boundaries blur: list_sessions overlaps with list_profiles filtered by status=running, batch_generate_profiles overlaps with create_profile, and page_snapshot/page_extract_text/page_screenshot all read the same page in different formats. Descriptions generally resolve these, but an agent must read carefully to choose correctly.
Nearly everything is snake_case verb_noun (list_profiles, create_group, stop_run, assign_proxy), with a consistent page_ namespace for browser actions. Minor deviations exist: page_snapshot, page_screenshot, profile_health and workspace_summary are noun-first rather than verb-first, and check_proxy vs get_proxy_health use different verbs for related checks.
At 39 tools this is well above the typical well-scoped range, and the surface spans many sub-domains (page control, profiles, proxies, groups, macros, runs, memory). Several tools could be consolidated or are redundant (list_sessions vs list_profiles, batch_generate_profiles vs create_profile), making the set feel heavy rather than tight.
Coverage is broad — browser control, profile lifecycle, proxy assignment/rotation/health, groups, macros, runs, memory and warming are all present. However, there are notable gaps: no tool to add a user-supplied proxy (only find_free_proxies and list_proxies), and no delete operations for profiles, groups, macros or proxies, plus no page back/forward or tab management. Agents will hit dead ends for these common lifecycle operations.