Skip to main content
Glama
SoftGlaze Browser MCP

SoftGlaze Browser MCP

Related Servers

Alternatives to SoftGlaze Browser MCP

Related Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables 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.
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Connects 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 npm
    Do What The F*ck You Want To Public
  • A
    license
    Not graded
    quality
    A
    maintenance
    Connects 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 npm
    MIT
  • A
    license
    C
    quality
    C
    maintenance
    Manage 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.
    59
    142 npm
    24
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Exposes 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.
    -

TDQS

B3.4/5.0

Scored across 39 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues