Chrome DevTools MCP Skill

Use this skill to run Chrome DevTools MCP operations through uxc using a fixed stdio endpoint.

Reuse the uxc skill for generic MCP discovery, daemon reuse, JSON envelope parsing, and error handling.

Prerequisites

• - uxc is installed and available in PATH.
• INLINECODE4 is available in PATH (Node.js installed).
• Chrome 144+ is running locally with remote debugging enabled from chrome://inspect/#remote-debugging if you use the default live-browser flow.
• Network access is available for first-time chrome-devtools-mcp package fetch.

Core Workflow (Chrome DevTools MCP-Specific)

Endpoint candidate inputs before finalizing:

• - Raw package form from official docs:

• - Reliable non-interactive form:

• - Default live-browser endpoint for this skill:

• - Explicit browser-url endpoint:

• - Fallback isolated endpoint:

• - Running local Chrome auto-connect mode:

1. 1. Verify protocol/path from official source and probe:

1. 2. Detect auth requirement explicitly:

1. 3. Use a fixed link command by default:

1. 4. Inspect operation schema before execution:

1. 5. Prefer read-first interaction:

1. 6. Confirm before mutating page state:

Guardrails

• - Keep automation on the JSON output envelope; do not rely on --text.
• Use chrome-devtools-mcp-cli as the default command path.
• Prefer the live-browser default endpoint when you need real logged-in state, current tabs, network diagnostics, console inspection, or performance analysis.
• Prefer --autoConnect first when browser-side remote debugging is available.
• Use chrome-devtools-mcp-port only when you intentionally run a Chrome instance with --remote-debugging-port=9222.
• If no debuggable Chrome is available, fallback to chrome-devtools-mcp-isolated.
• Prefer take_snapshot over screenshots for model-action loops.
• Prefer list_network_requests / get_network_request over raw script evaluation when inspecting network behavior.
• Treat lighthouse_audit, performance_start_trace, and take_memory_snapshot as heavier operations; use them intentionally.
• Use evaluate_script only when an existing higher-level DevTools tool cannot answer the question.

References

• - Invocation patterns: