Session-local Chrome launcher for Chrome DevTools MCP workflows.
Until 2026-09-26 this record combined several servers published from one repository. The others now have records of their own: chrome-devtools-mcp-wrapper. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"chrome-devtools-mcp-canpoint","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# chrome-devtools-mcp-wrapper Session-local Chrome launcher for Chrome DevTools MCP workflows. - Repository: https://github.com/mjwyr/chrome-devtools-mcp-canpoint.git - Author: 若清风 This wrapper gives each MCP server process its own random remote debugging port and generated user data directory, so multiple agent sessions do not fight over port `9222` or a shared Chrome profile. By default, the actual Chrome process is started lazily: normal MCP startup and tool discovery can complete without opening a browser. In lazy mode the wrapper answers `tools/list` from the official `chrome-devtools-mcp` package metadata, then launches Chrome only when the conversation first calls a browser-backed MCP tool. On Windows it also resolves common command shims such as `npx.cmd`, so downstream MCP commands can be passed as normal argument lists. ## Usage Run it directly with `uvx`: ```powershell uvx chrome-devtools-mcp-wrapper -- <downstream-mcp-command> ``` Example: ```powershell uvx chrome-devtools-mcp-wrapper -- npx -y chrome-devtools-mcp@latest --browser-url={browser_url} ``` By default, Chrome starts in lazy mode and uses quiet window startup once a browser-backed tool is called. Quiet mode keeps Chrome headful for compatibility, adds `--start-minimized`, and uses a best-effort non-activating minimized startup on Windows. It reduces focus stealing but cannot guarantee Chrome or the OS will never focus the window. Preserve the old startup-time launch behavior with: ```powershell uvx chrome-devtools-mcp-wrapper --launch-mode eager -- <downstream-mcp-command> ``` Force a fully headless browser with either option: ```powershell uvx chrome-devtools-mcp-wrapper --window-mode headless -- <downstream-mcp-command> uvx chrome-devtools-mcp-wrapper --headless -- <downstream-mcp-command> ``` If Chrome is not installed in the default Windows location, pass it explicitly: ```powershell uvx chrome-devtools-mcp-wrapper --chro…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.