chrome-devtools-mcp and camofox-mcp
These are complements: ChromeDevTools provides standard browser automation capabilities for web interaction, while camofox-mcp adds anti-detection evasion techniques on top to prevent blocking during automated navigation—tools that would be used together when standard automation fails due to bot detection.
About chrome-devtools-mcp
ChromeDevTools/chrome-devtools-mcp
Chrome DevTools for coding agents
Implements a Model-Context-Protocol (MCP) server that bridges AI coding agents with Chrome's DevTools Protocol, enabling performance tracing, network inspection, and automated browser actions through Puppeteer. Supports both full-featured and lightweight ("slim") modes, integrating with agents like Claude, Gemini, and Cursor for debugging, screenshot capture, and source-mapped stack trace analysis.
About camofox-mcp
redf0x1/camofox-mcp
Anti-detection browser MCP server for AI agents — navigate, interact, and automate the web without getting blocked
Exposes 46 specialized browser automation tools (navigation, interaction, observation, downloads, batch workflows) via MCP stdio or HTTP transport, connecting Claude Desktop, VS Code, Cursor, and OpenClaw to a separate CamoFox browser server. Built on Camoufox anti-detection techniques with token-efficient accessibility snapshots, CSS-selector fallbacks, and session persistence including cookie import and profile management. Supports both desktop MCP clients via stdio and remote agents via HTTP, with optional API-key authentication and batch workflow coordination across tracked tabs.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work