chrome-devtools-mcp vs google-surf-mcp
chrome-devtools-mcp: chrome-devtools-mcp enables AI coding assistants like Gemini, Claude, and Copilot to interact with a live Chrome browser via the Model-Context-Protocol (MCP). It grants AI full access to Chrome DevTools for reliable automation, deep debugging, and detailed performance insights.; google-surf-mcp: A Google Search MCP server that requires no API key, uses Playwright with stealth techniques to avoid detection, handles CAPTCHA by opening a Chrome window for human solving, and provides five tools: search, search_parallel, extract, search_extract, and health. Designed for local use, with optional cloud mode for headless environments.
TL;DR
- You want an agent to record a Chrome performance trace and get insights from it; the README lists performance_start_trace, performance_stop_trace and performance_analyze_insight.
- You need to inspect network requests, console messages and screenshots of a page while debugging it.
- You want the agent to attach to a Chrome you already have running, using --browser-url, --ws-endpoint or --autoConnect (Chrome 144+).
- You need Firefox or Safari: the project is built on Chrome DevTools and targets Chrome.
- You want a general-purpose automation or test runner across browsers; Playwright MCP is the closer fit.
- You cannot run Node.js 20.19 or newer, which the README lists as a requirement.
Integrating Google search into AI agents without API key
Side-by-Side Comparison
chrome-devtools-mcpgoogle-surf-mcpFeatures
chrome-devtools-mcpgoogle-surf-mcpUse Cases
chrome-devtools-mcpgoogle-surf-mcpBest For
chrome-devtools-mcpgoogle-surf-mcpFAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.