Context Switching Overhead
Constantly switching between IDE, browser, and DevTools breaks your flow and slows down debugging significantly.
AI writes code but can it verify its own output? Find bugs and fix them? With Browser DevTools MCP, your AI gets eyes and hands in the browser and backend. Frontend + backend debugging. Use as MCP server, VS Code/Cursor extension, CLI, skills, or Claude plugin. Let your agent see, interact, and debug autonomously.
AI coding assistants generate code fast, but verifying it and debugging when things break requires full context. Without eyes in the browser and hands on the backend, your AI can't see what's wrong—or fix it. Full-stack debugging stays manual and fragmented.
Constantly switching between IDE, browser, and DevTools breaks your flow and slows down debugging significantly.
When issues occur in production, you're often left guessing. Logs tell only part of the story.
Reproducing bugs requires manual steps, setting up state, and navigating through complex user flows.
Frontend vs backend two separate worlds. Network, console, DOM, and API state are scattered across tools and contexts.
Your AI generates code quickly, but without runtime access it can't see what breaks, find root causes, or fix issues—you debug alone.
Browser DevTools MCP gives AI coding assistants direct access to browser and backend debugging. See what your users see, debug APIs and servers, and fix issues frontend to backend through MCP, VS Code/Cursor extension, CLI, skills, or Claude plugin.
Browser (Playwright) for frontend—plus backend platform. Attach to API servers and processes. Tracepoints, logpoints, exception monitoring across the entire stack.
Capture screenshots with optional annotated overlays (ref labels, content, cursor-interactive elements). Let AI see exactly what's rendered. Compare against Figma designs with AI-powered similarity scoring.
Navigate, click, fill forms, scroll, and interact with any element. Use CSS selectors or ARIA refs (e1, @e1) from snapshots for reliable targeting. Your AI can reproduce any user journey automatically.
Monitor HTTP requests, capture console logs and errors, and track network failures in real-time.
Measure Core Web Vitals (LCP, FID, CLS), identify performance bottlenecks, and optimize with data-driven insights.
ARIA and AX tree snapshots with refs for interaction. Bounding boxes, occlusion detection, interactive-only or cursor-interactive filters. Ensure your application works for everyone.
Inspect React component trees, examine props and state, and understand your component hierarchy.
Stub API responses, intercept network requests, and test edge cases without modifying your backend.
OpenTelemetry integration for end-to-end request tracing. Follow requests from browser to backend and back.
Set tracepoints, logpoints, and exception handlers without pausing execution. Monitor DOM mutations and network requests with snapshot capture.
browser-devtools-cli for frontend, node-devtools-cli for backend. Script automation, session-based debugging, and daemon architecture. Use standalone or via skills.
Install full-stack debugging capabilities as skills for AI coding agents like Claude Code, Cursor, and Windsurf. One command adds browser + backend debugging via the skills.sh ecosystem. Also available as VS Code/Cursor extension and Claude Plugin.
npx skills add serkan-ozal/browser-devtools-skills
Browser automation, interaction, and form testing. Navigate pages, fill forms, test validation flows.
Full-stack: web and backend. Console, network, tracepoints, logpoints, and exception monitoring.
Annotated screenshots, responsive testing, and Figma design comparison for pixel-perfect implementations.
Web Vitals (LCP, INP, CLS) measurement and performance analysis with actionable recommendations.
WCAG compliance, ARIA snapshots with refs, AX tree with occlusion detection. Use refs for interaction tools.
API mocking, request interception, and response stubbing for edge case testing.
React component inspection, props and state examination, and component hierarchy visualization.
Distributed tracing with OpenTelemetry, trace ID management, and backend correlation.
AI coding assistants write code fast—but the real power comes when they can see it run, find bugs, and fix them. Browser DevTools MCP gives your AI eyes in the browser and hands on the backend. Full-stack debugging: frontend to backend, in one flow.
We believe the future of development is AI that doesn't just generate code—it verifies it, debugs it, and iterates. No more blind spots between "AI wrote it" and "it works." MCP server, VS Code/Cursor extension, CLI, skills, or Claude plugin—choose how your AI debugs.
Whether you're building a new feature, debugging a tricky issue, or monitoring production, Browser DevTools MCP adapts to your workflow.
Let your AI assistant see your running application, interact with UI elements, and debug issues in real-time. No more copy-pasting error messages or describing what you see—your AI has full visual and interactive context.
Generate comprehensive test scenarios by letting AI explore your application. Capture visual snapshots, verify functionality, and catch regressions before they reach users.
Connect to your production environment and let AI investigate issues with the same tools you use locally. Capture state, analyze network requests, and identify root causes without the guesswork.
Compare your implementation against Figma designs with AI-powered visual analysis. Identify discrepancies, measure spacing, and ensure your UI matches design specifications.
MCP server, VS Code/Cursor extension (one-click install, no config), Claude Plugin (skills + commands + agents), or manual config. Full-stack debugging for Cursor, Claude, VS Code, Windsurf, Copilot, and Gemini.
{
"mcpServers": {
"browser-devtools": {
"command": "npx",
"args": ["-y", "browser-devtools-mcp"]
}
}
}
{
"mcp": {
"servers": {
"browser-devtools": {
"type": "stdio",
"command": "npx",
"args": ["-y", "browser-devtools-mcp"]
}
}
}
}
One-click install—no manual MCP config. The extension bundles the MCP server and runs it automatically. Full-stack debugging (browser + backend) in Cursor or VS Code with Copilot.
# VS Code
code --install-extension serkan-ozal.browser-devtools-mcp-vscode
# Cursor
cursor --install-extension serkan-ozal.browser-devtools-mcp-vscode
Recommended for Claude Code users. Adds skills, slash commands (/browse, /screenshot, /webvitals, etc.), and agents (accessibility-auditor, design-qa, performance-analyzer). Full-stack debugging: browser + backend.
# Add marketplace
/plugin marketplace add serkan-ozal/browser-devtools-claude
# Install
/plugin install browser-devtools-mcp@serkan-ozal/browser-devtools-claude
{
"mcpServers": {
"browser-devtools": {
"command": "npx",
"args": ["-y", "browser-devtools-mcp"]
}
}
}
claude mcp add browser-devtools -- npx -y browser-devtools-mcp
{
"mcpServers": {
"browser-devtools": {
"command": "npx",
"args": ["-y", "browser-devtools-mcp"]
}
}
}
{
"mcpServers": {
"browser-devtools": {
"type": "local",
"command": "npx",
"args": ["-y", "browser-devtools-mcp"]
}
}
}
{
"mcpServers": {
"browser-devtools": {
"command": "npx",
"args": ["-y", "browser-devtools-mcp"]
}
}
}
Give your AI eyes in the browser and hands on the backend. MCP, VS Code/Cursor extension, CLI, skills, or Claude plugin—start verifying and fixing code with AI.