MCP Server for Chrome browser automation via debugging protocol with session persistence
Chrome debug mcp mcp server lets Claude, Cursor and other MCP clients work with Chrome Debug MCP directly. MCP Server for Chrome browser automation via debugging protocol with session persistence.
A Model Context Protocol (MCP) server for Chrome browser automation via debugging protocol, specifically designed to connect to Chrome debugging ports and enable browser automation with persistent login sessions.
The server is distributed via npm as chrome-debug-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Browser automation servers are the ones people reach for when a site has no API — the assistant drives a real page instead of guessing at endpoints. Chrome Debug MCP sits in that group. Worth comparing against the other browser automation servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
> ```json
> {
> "mcpServers": {
> "browser-automation": {
> "command": "chrome-debug-mcp"
> }
> }
> }
>Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.