What problem does it solve? Web projects need agent-facing browser control, but manually wiring an MCP server into project configuration is error-prone and risks clobbering existing entries. This Skill converges the chrome-devtools-mcp server into the project's .mcp.json idempotently, so running it repeatedly verifies and repairs rather than duplicating or overwriting. ## Core Features & Use Cases - Merge-never-clobber configuration: Adds the chrome-devtools server entry to .mcp.json without touching other entries, and refuses to overwrite deliberate local variants. - Prerequisite checks: Verifies Node.js 20+ and Chrome stable are installed, reporting what to install while still writing the inert configuration. - Migration and flagging: Upgrades the suite's previous default entry to the per-project profile version, and flags superseded hand-rolled CDP-attach browser kits without deleting anything. - Use Case: Run /setup-web in a new web project to give the agent full browser control — navigation, clicks, screenshots, console messages — via a headed Chrome with a persistent per-project profile. ## Quick Start Run the /setup-web slash command in your web project to configure the chrome-devtools-mcp server in .mcp.json, then restart the session and verify with /mcp.