chrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility.
Scanned 9/12/2026
Install to Claude Code
Skills Directorynpx -y skills add srid/emanote --skill nix-chrome-devtools-mcp --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Nix Chrome Devtools Mcp?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/srid-nix-chrome-devtools-mcp-emanote)More formats (shields.io, HTML) on the badges page.
---
name: nix-chrome-devtools-mcp
description: chrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility.
user-invocable: false
---
# nix-chrome-devtools-mcp
Drop-in launcher for the [Chrome DevTools MCP server](https://github.com/ChromeDevTools/chrome-devtools-mcp). Self-contained — `bin/serve` resolves all inputs via `nix build` / `nix shell`.
Full docs in the [repo README](https://github.com/juspay/nix-chrome-devtools-mcp/blob/main/README.md).
This skill primitive exists for APM's deployment convention — it ensures `bin/serve` lands at `.agents/skills/nix-chrome-devtools-mcp/bin/serve` in the consumer's working tree (per APM's [skills convergence](https://microsoft.github.io/apm/reference/targets-matrix/#skills-convergence) path), which keeps the launcher available even before `apm install` runs on a fresh clone. The package is mechanically a "skill" in APM's primitive vocabulary; semantically it's a tool.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
