cloakbrowser-mcp
Related Servers
Alternatives to cloakbrowser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to perform stealth browser automation with anti-detection, including navigation, clicking, typing, screenshots, and network monitoring via an MCP server.MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigating, clicking, typing, taking screenshots, inspecting pages, and running multi-step automated tests. It also supports visual regression, session recording, and network/console monitoring through MCP tools.106 npmMIT
- AlicenseBqualityBmaintenanceUse your signed-in Chrome through a local MCP server and companion extension. Supports tabs, navigation, forms, screenshots, and page reading, with a deny-all domain allowlist. Install: npx -y mcp-browser-extension@latest.22684 npm6MIT
- FlicenseNot gradedqualityDmaintenanceProvides browser automation capabilities through Claude Desktop and other MCP clients, enabling navigation, screenshot capture, content extraction, and interactive control.-
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigation, interaction, screenshots, accessibility snapshots, network and console monitoring, and automated end-to-end testing through MCP tools.106 npmMIT
- AlicenseCqualityCmaintenanceEnables MCP clients such as Claude to drive the user's real Chrome in the background via the DevTools Protocol through a companion extension, exposing 32 tools for navigation, form input, screenshots, snapshots, script evaluation, network and console inspection, performance tracing and raw CDP commands, with control off by default and limited by allowed sites and blocked domains.3225 npm1MIT
TDQS
Scored across 55 tools
Most tools have distinct roles, but there is noticeable overlap between navigate and read_url, get_text/get_markdown/get_html/find_in_page, screenshot and screenshot_file, and run_steps versus the individual action tools. The descriptions usually clarify which to use, but with 55 tools an agent still faces a real selection burden.
The set is mostly snake_case and readable, but conventions are mixed: list_downloads and tab_new use verb-first naming, while tabs_list is noun-first. Some tools are verb-only (click, hover, reload), others are noun-oriented or adjective-led (fingerprint_info, new_identity), so the pattern is not fully predictable.
55 tools is heavy for a single server even given the broad browser-automation scope. Several groups could be consolidated or made more discoverable, and the sheer surface increases the chance of misselection despite many tools earning their place individually.
The surface covers navigation, tabs, interaction, extraction, screenshots/PDFs, cookies/sessions, downloads, network/console, proxy/fingerprint, stealth checks, and memory. Coverage is strong, with only minor gaps such as explicit iframe switching or drag-and-drop, which agents can largely work around via snapshot refs, evaluate, or run_steps.