chrome-mcp-bootstrap

Restart chrome-devtools-mcp and verify Chrome MCP connection readiness.

63|8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/different-ai/the-factory --skill chrome-mcp-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-mcp-bootstrap
Source: https://github.com/different-ai/the-factory/tree/main/.opencode/skills/chrome-mcp-bootstrap
Command: npx skills add https://github.com/different-ai/the-factory --skill chrome-mcp-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @different-ai/opencode-browser, chrome-devtools-mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users quickly resolve issues where the Chrome MCP (Message Communication Protocol) connection is broken or unavailable, which is crucial for UI-driven browser automation and testing.

Core Features & Use Cases

  • Troubleshooting Connection Issues: Addresses common problems like a missing browser broker or inability to connect to MCP.
  • Automated Repair Steps: Provides a sequence of commands to restart the MCP process and ensure Chrome is running.
  • Readiness Checks: Includes methods to verify the MCP connection status through different paths (extension vs. direct DevTools).
  • Use Case: When automated tests fail due to a flaky browser connection, this skill can be invoked to diagnose and fix the MCP issue before re-running the tests.

Quick Start

Run the provided commands to restart the chrome-devtools-mcp process and attempt to reconnect.

Frequently Asked Questions about chrome-mcp-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a flaky Chrome MCP connection for browser automation testing?

To fix a flaky Chrome MCP connection, restart the chrome-devtools-mcp process and ensure Chrome is running. This recovers local issues and restores the browser connection for UI-flow testing.

Why does my Chrome MCP connection keep dropping during UI testing?

Your Chrome MCP connection drops due to local issues like a missing browser broker or crashed chrome-devtools-mcp process. Restarting the process and verifying Chrome is running resolves the broken connection.

How do I verify if my Chrome MCP connection is ready for automated tests?

You verify the Chrome MCP connection by performing minimal readiness checks via the browser plugin path or direct Chrome DevTools MCP paths to ensure the connection is active before running tests.

Does the Chrome MCP repair process work with the browser plugin and Chrome DevTools?

Yes, the repair process works with both the browser plugin and Chrome DevTools MCP. It performs readiness checks through these paths to verify the connection status after restarting the chrome-devtools-mcp process.

What should I do when chrome-devtools-mcp is missing or fails to connect?

When chrome-devtools-mcp is missing or fails to connect, run automated repair commands to restart the MCP process and ensure Chrome is running, which recovers local browser connection issues for your tests.