In-depth architectural comparison of the MCP Browser Agent and Cloakbrowser MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Browser Agent
Browser Automation · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Cloakbrowser MCP
Browser Automation · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Browser Agent if you need specialized Browser Automation tools running via a local process. Choose Cloakbrowser MCP if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Browser Agent when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: MCP_BROWSER_TYPE.
MCP Browser Agent is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Cloakbrowser MCP belongs to Browser Automation using local stdio subprocess. Select MCP Browser Agent when you need capabilities focused on browser automation and Cloakbrowser MCP when you require tools for browser automation.
Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.
browser_find
Search the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.