Skip to main content
Glama
ColorSource

cloakbrowser-mcp

by ColorSource
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cloakbrowser-mcp

No user-submitted related servers found.

    Related Servers

    • cloak-browser-mcp

      devinwang
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to drive a source-patched stealth Chromium through the Model Context Protocol, exposing 86 Playwright-compatible browser automation tools for navigation, interaction, tabs, forms, screenshots, and page-state inspection. Adds persistent profiles, proxy/GeoIP-aware emulation, humanized input, and built-in stealth auditing so automated sessions pass Cloudflare Turnstile, reCAPTCHA v3, FingerprintJS, and similar bot detection.
      35
      106 npm
      2
      MIT

    • Camoufox Unified MCP Server

      tom613951
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform stealth browser automation and anti-detection web interaction, including session management, humanized interactions, and bypassing anti-bot/WAF protections.
      MIT

    • Stealth Browser MCP

      burgebj
      A
      license
      Not graded
      quality
      D
      maintenance
      Undetectable browser automation for AI agents that bypasses Cloudflare, antibot systems, and social media blocks using real browser instances with 97 tools across 11 sections.
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.8/5.0

    Scored across 28 tools

    Disambiguation5/5

    Each tool has a distinct purpose, covering specific browser actions like clicking, typing, scrolling, navigating, and extracting data. There is no overlap; even similar-sounding tools like browser_snapshot, browser_screenshot, and browser_read_page serve clearly different needs.

    Naming Consistency5/5

    All tools follow a consistent `browser_verb` pattern in snake_case, such as browser_launch, browser_click, browser_new_page. This predictable naming makes it easy for an agent to infer functionality.

    Tool Count4/5

    With 28 tools, the count is higher than the typical 3-15 range for a well-scoped server. However, the complex domain of browser automation justifies this many operations, and each tool serves a unique and necessary function.

    Completeness5/5

    The tool set covers the full lifecycle: launch, page management, navigation, interaction, data extraction, network control, cookies, and PDF generation. Only minor features like page refresh or file upload are missing, but the core workflows are fully supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources