CloakBrowser vs browser-rs-mcp
Browser automation tools for scraping and AI agents compared
CloakBrowser and browser-rs-mcp both support browser automation for scraping, QA, and AI-agent workflows. CloakBrowser uses a custom Chromium build with Python and JavaScript APIs, while browser-rs-mcp is a Rust MCP server for sharing a Chrome profile across agents.
CloakBrowser: Automate Chromium with Modified Fingerprints
CloakBrowser wraps a custom Chromium build with source-level fingerprint changes and Playwright- and Puppeteer-compatible APIs. It is aimed at browser automation and web scraping where standard browser automation is frequently flagged by bot detection.
browser-rs-mcp: Share Chrome with AI Agents
A Rust MCP server that lets multiple AI agents control separate tabs in one shared Chrome profile. It provides browser automation through Chrome DevTools Protocol without requiring a Node.js runtime.
| CloakBrowser | browser-rs-mcp | |
|---|---|---|
| Language | Python | Rust |
| License | MIT | Apache-2.0 |
| Stars | 31.9k | 25 |
| Forks | 2.6k | 3 |
| Last analyzed | Oct 3, 2026 | Oct 4, 2026 |
Key differences
- CloakBrowser modifies fingerprint and automation signals in custom Chromium builds, while browser-rs-mcp uses Chrome DevTools Protocol and does not promise detection bypass.
- CloakBrowser offers Playwright-compatible APIs for Python and JavaScript plus a JavaScript Puppeteer entry point; browser-rs-mcp exposes browser tools to MCP clients.
- CloakBrowser downloads and caches its browser binary, while browser-rs-mcp requires locally installed Chrome or Chromium.
- CloakBrowser is licensed under MIT, while browser-rs-mcp is licensed under Apache-2.0.
- CloakBrowser focuses on automated browsing with persistent contexts and optional human-like input; browser-rs-mcp focuses on multiple agents sharing one browser process with owner-scoped tabs.
- CloakBrowser has 31.9k stars and 2.6k forks; browser-rs-mcp has 25 stars and 3 forks.
Choose CloakBrowser if you…
- need a custom Chromium build with source-level fingerprint changes.
- want Playwright-compatible Python or JavaScript APIs, or a JavaScript Puppeteer entry point.
- need persistent browser contexts, proxy configuration, or optional human-like input.
Choose browser-rs-mcp if you…
- want multiple AI agents to use one Chrome process and persistent profile in separate owner-scoped tabs.
- need an MCP server with stdio or HTTP transports and no Node.js runtime.
- want browser tools such as snapshots, screenshots, page inspection, and interaction through Chrome DevTools Protocol.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.