Stateful Browser Automation Via Mcp

via “remote-browser-automation-via-devtools-protocol”

MCP server for Chrome DevTools

Unique: Bridges MCP protocol directly to Chrome DevTools Protocol without intermediate abstraction layers like Puppeteer or Playwright, reducing dependency overhead and enabling direct access to low-level CDP capabilities. Implements streaming response handling for long-running operations through MCP's resource and tool call patterns.

vs others: Lighter-weight than Puppeteer/Playwright-based MCP servers because it eliminates the extra abstraction layer, providing direct CDP access while maintaining MCP compatibility for seamless AI agent integration.