Skip to main content
Glama
devinwang

cloak-browser-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to cloak-browser-mcp

No user-submitted related servers found.

    Related Servers

    • stealthy-auto-browse MCP

      psyb0t
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a stealthy browser via the Model Context Protocol, supporting navigation, screenshots, clicking, typing, and more.
      94
      Do What The F*ck You Want To Public

    • CloakBrowser MCP

      james93974
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a Chromium-based browser for web research, testing, and automation with Playwright-compatible tools, persistent profiles, proxy matching, extension loading, and humanized input across local or containerized deployments.
      784 npm
      MIT

    • CloakBrowser MCP

      Heather7327
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to automate real Chromium browsing through Playwright-compatible tools, including humanized interactions, persistent profiles, proxy matching, and npm/Docker or stdio/Streamable HTTP deployment.
      784 npm
      MIT

    • cloakbrowser-mcp

      ColorSource
      A
      license
      A
      quality
      D
      maintenance
      Stealth browser automation for AI agents, using source-patched Chromium to bypass bot detection systems like Cloudflare, reCAPTCHA, and FingerprintJS.
      28
      Apache 2.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3.1/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools have a clearly distinct action (click, hover, type, scroll, evaluate), and descriptions are detailed enough to separate them in most cases. However, a few pairs overlap meaningfully: browser_type vs browser_fill_form, browser_drag vs browser_drop, and the three cloak audit tools (detection_test, stealth_audit, request_signal_inspect) all serve similar verification goals, so an agent could hesitate.

    Naming Consistency3/5

    All names use snake_case with predictable browser_ and cloak_ prefixes, which is readable. But verb position is inconsistent across the server: the browser_ namespace is mostly verb-first, while cloak_ mixes verb-first set_* tools with noun-first names like persistent_profile_list, detection_test, and request_signal_inspect, so conventions are mixed rather than uniform.

    Tool Count3/5

    35 tools is heavy for a single server, and the surface includes granular operations like browser_drag and browser_drop that could plausibly be merged. The count is somewhat justified because the server spans two large domains (browser control and fingerprint/stealth management), but it still sits well above the typical well-scoped range.

    Completeness4/5

    Core browser automation (navigation, interaction, forms, snapshots, screenshots, console, waiting, JS evaluation) and stealth configuration (fingerprint, timezone, locale, geolocation, proxy, profiles, binary management) are broadly covered. Missing are common browser-management operations such as cookie/storage access, network interception or route mocking, download handling, and explicit context/browser teardown, which leaves some minor workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources