CloakBrowser MCP
Related Servers
Alternatives to CloakBrowser MCP
- AlicenseAqualityNot gradedmaintenanceEnables browser automation through Playwright using accessibility tree snapshots instead of screenshots. Supports web scraping, form interactions, testing, and connecting to existing browser sessions with logged-in accounts.233,012 npm5-
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and clients to drive and test real web browsers through the full upstream Playwright MCP tool surface, backed by CloakBrowser Chromium with persistent profiles, proxy matching, and humanized mouse, keyboard, and scroll behavior. It can be installed via npm or Docker and run over stdio or Streamable HTTP with multi-session support.784 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a drop-in Playwright MCP-compatible browser automation server backed by CloakBrowser Chromium, letting AI agents run unchanged upstream browser tools over stdio or Streamable HTTP via npm or Docker. It adds persistent browser profiles, managed CDP access, GeoIP-aware proxies, and humanized mouse, keyboard, and scroll behavior for interaction-sensitive automation.784 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive real browser automation through an unchanged Playwright MCP tool surface backed by CloakBrowser Chromium, with persistent profiles, proxy matching, humanized input, and npm, Docker, or Streamable HTTP deployment.784 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.3,154 npm57-
- FlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to control a browser through Playwright, supporting tasks like navigation, typing, clicking, and taking screenshots.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to automate browser interactions using Playwright and Cloudflare Workers, supporting tasks like navigation, clicking, typing, and screenshots.3,012 npmApache 2.0
TDQS
Scored across 25 tools
Several tools have closely related purposes, such as browser_drag vs browser_drop, browser_close vs browser_tabs, and browser_fill_form vs browser_type. The descriptions mostly clarify the differences, but an agent could still easily select the wrong one in edge cases.
The browser_ prefix is consistent, but the naming patterns vary between bare verbs (browser_click), verb+object (browser_select_option), and noun phrases (browser_tabs, browser_file_upload). The two cloakbrowser_* info tools also break the overall naming scheme, though they are clearly metadata-oriented.
At 25 tools, this is on the heavier end for a tool set. Most tools serve a real browser-automation purpose, but a few are arguably redundant or very niche, and the two metadata info tools add little practical value.
The domain of browser automation is well covered: navigation, page interaction, forms, uploads, dialogs, console, network requests, tabs, and snapshots are all present. Missing pieces like reload, forward navigation, and cookie/storage management are gaps, but agents can work around them using browser_navigate or browser_evaluate.