This MCP allows you to record browser interactions with a chrome extension that include screenshots and console logs. The data is then saved to a
This MCP allows you to record browser interactions with a chrome extension that include screenshots and console logs. The data is then saved to a local database
A Model Context Protocol (MCP) implementation for browser automation using Playwright, with full Greasemonkey API support.
The server publishes 2 tools. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverSetup — The Setup tool exposed by this serverCompare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"chrome-debug": {
"command": "node",
"args": [
"path/to/chrome-debug-mcp/build/index.js"
],
"disabled": false,
"alwaysAllow": []
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
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.
Enables AI-powered applications to monitor and interact with browser data via a Chrome extension and MCP.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript