By serkan-ozal
Multi-platform DevTools MCP: Playwright browser automation and non-blocking Node.js backend debugging for Claude Code
npx claudepluginhub serkan-ozal/browser-devtools-claude --plugin browser-devtools-mcpRun accessibility analysis on the current page using ARIA snapshots and AX tree
Navigate back in browser history
Navigate to a URL and interact with web pages using Browser DevTools MCP
Click an element on the page by selector or ref
Get console messages from the browser
Drag an element to a target location by selector or ref
Batch tool calls via JavaScript (no slash command; use from agent/skill or MCP)
Compare the current page with a Figma design
Fill an input field with text by selector or ref
Navigate forward in browser history
Hover over an element on the page by selector or ref
Get HTML content from the current page
Intercept HTTP requests matching a pattern
Press a key or key combination
Mock HTTP responses for testing
Monitor and inspect HTTP network requests
Configure and inspect OpenTelemetry instrumentation
Save the current page as a PDF file
Inspect React components on the page
Reload the current page
Resize the browser viewport
Execute JavaScript code in the browser
Take a screenshot of the current browser page or a specific element
Scroll the page or an element
Select an option from a dropdown or select element by selector or ref
Get visible text content from the current page
Manage OpenTelemetry trace IDs for distributed tracing
Wait for network activity to become idle
Get Core Web Vitals metrics from the current page
Connect to a Node.js process for debugging via V8 Inspector
Disconnect from the connected Node.js process
Configure exception breakpoints to capture snapshots on exceptions
Batch tool calls via JavaScript (no slash command; use from agent/skill or MCP)
Set a logpoint to evaluate and log expressions without pausing
Get console output from the connected Node.js process
Execute JavaScript in the connected Node.js process
Get captured tracepoint, logpoint, or exceptionpoint snapshots
Get debugging status of the connected Node.js process
Set a tracepoint to capture call stack and variables without pausing
Audits web pages for WCAG compliance and accessibility issues
Default Browser DevTools MCP agent — ARIA/snapshot-first workflow, execute for run JS and batch, ref-based interaction
Compares web implementations with Figma designs for visual QA
Evaluates web page performance using Core Web Vitals and network analysis
Performs comprehensive web application testing for functionality and usability
Extracts structured data from web pages with navigation and dynamic content support
Automated browser testing and debugging using Browser DevTools MCP. Use when testing web pages, debugging frontend issues, verifying UI behavior, or automating browser interactions.
Use when the user wants to run JavaScript in the browser, run code in Node, or batch multiple MCP tool calls. Run script, execute code, batch tools.
Debug Node.js backend processes using non-blocking tracepoints, logpoints, exceptionpoints, and JavaScript execution. Use when debugging API servers, workers, or backend scripts.
Monitor and debug web applications using OpenTelemetry, console logs, network requests, and distributed tracing. Use when correlating frontend and backend requests or debugging request flow across services.
Analyze web page performance using Web Vitals and network timing metrics. Use when optimizing load times, checking Core Web Vitals, or investigating slow pages.
Perform visual testing and UI verification using screenshots and DOM inspection. Use when verifying UI appearance, comparing with designs, or checking for visual regressions.
Debug web applications by inspecting console logs, network requests, JavaScript errors, and using non-blocking tracepoints/logpoints. Use when debugging web pages, inspecting API calls, or tracing code execution.
Claude Plugin for Browser DevTools MCP — Playwright browser automation and non-blocking Node.js backend debugging. Compatible with browser-devtools-mcp 0.3.x.
npx — the MCP server runs as an npm package)/plugin/plugin marketplace add serkan-ozal/browser-devtools-claude/plugin install browser-devtools-mcp@serkan-ozal/browser-devtools-claudeExample — add to ~/.claude/settings.json (see CONFIG.md for more):
{
"mcpServers": {
"browser-devtools": {
"command": "npx",
"args": ["-y", "browser-devtools-mcp@latest"],
"env": {
"PLATFORM": "browser",
"BROWSER_HEADLESS_ENABLE": "true"
}
},
"node-devtools": {
"command": "npx",
"args": ["-y", "browser-devtools-mcp@latest"],
"env": {
"PLATFORM": "node"
}
}
}
}
The plugin includes both browser and node MCP servers by default. This manual setup gives you the MCP tools without the plugin's skills, commands, or agents. See CONFIG.md for all environment variables.
Commands are split by platform. See docs/commands/.
Browser (PLATFORM=browser): /browse, /screenshot, /click, /fill, /hover, /accessibility, /console, /network, /webvitals, /figma, /run-js, and more — see commands/browser/.
Node (PLATFORM=node): /connect, /disconnect, /tracepoint, /logpoint, /snapshots, /run-js-node, and more — see commands/node/. Execute (batch): see commands/node/execute.md.
When the plugin is enabled, the default agent is applied automatically. It enforces: ARIA/snapshot first (not screenshot to understand structure), snapshot before any click/fill/hover, and execute for run JS and batch tool calls. You can switch to another agent via /agents or override the default (see CONFIG.md).
Use agents for focused tasks:
The plugin activates skills when you mention:
The plugin registers two MCP servers by default:
PLATFORM=browser)PLATFORM=node)Both are active at once; use browser commands for web pages and node commands for backend debugging.
The browser-devtools-mcp package also provides a CLI (browser-devtools-cli, node-devtools-cli) and an optional daemon. The execute tool (batch tool execution) is available via MCP, CLI subcommand run execute, and daemon API (POST /call).
Browser DevTools MCP - Playwright-powered browser automation for Claude Code
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Browser automation and debugging MCP servers: Chrome DevTools and Playwright
Playwright browser automation with E2E testing skill and responsive design testing agent.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Development tool providing browser-based environment for testing and debugging web applications and scripts.
Capture a full DevTools-protocol trace (CDP firehose, screenshots, DOM dumps) alongside any browser automation, then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-flight Browserbase session, or feed structured per-page summaries back into an agent loop.