chrome-devtools-mcp and kernel-mcp-server
These are complements: Chrome DevTools MCP exposes Chrome's debugging protocol for agent control, while Kernel MCP Server provides a managed cloud infrastructure layer for running browser automation at scale, so they could be used together where Kernel hosts the browser instance that Chrome DevTools MCP instruments.
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 kernel-mcp-server
kernel/kernel-mcp-server
Open-source MCP server for secure, low-latency cloud-browser automation on Kernel.
Implements core browser automation via Playwright scripts executed against live Chromium instances, with automatic video recording of sessions and real-time invocation monitoring. Authenticates through OAuth 2.0 with Clerk and supports multiple transport protocols (streamable HTTP, stdio via mcp-remote) for compatibility across AI assistants like Claude, Cursor, and VS Code.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work