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.8236,893 npm5-
Related Servers
- 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,667 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.6,893 npmApache 2.0

kitewrightofficial
AlicenseNot gradedqualityAmaintenanceA lightweight MCP server for browser automation that gives AI agents navigate, screenshot, and extract tools via a single small binary, without needing Node.js or Playwright. It provides CDP-based browser control with efficient startup and resource usage.23MIT- FlicenseNot gradedqualityBmaintenanceAn MCP server that lets AI assistants drive real Chromium browsers — navigate, click, type, read pages, run OCR, and record network traffic. 43 tools, credentials stay local, zero telemetry.-
- AlicenseNot gradedqualityBmaintenanceMCP server that bridges Model Context Protocol with browser automation, offering 37 tools across three modes (Playwright, CDP, Chrome Extension) and an autonomous agent for web tasks.MIT
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.