Session-local Chrome launcher for Chrome DevTools MCP workflows.
Listed on its own since 2026-09-26. Until then it was part of chrome-devtools-mcp-canpoint, where its earlier checks remain.
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-wrapper","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. ## Official MCP compatibility Wrapper **1.2.0** is verified against official **chrome-devtools-mcp 1.10.1** (latest stable checked on 2026-10-15). The bundled fallback contains the 30 default official tools, including `get_css_styles`, current page-ID routing, multi-file uploads, and console stack traces. Normal discovery reads the actual downstream package, including tools enabled through CLI flags or a JSON config. See [upgrade notes and feature options](docs/upstream-1.10.1.md). Official options go **after** `chrome-devtools-mcp@latest`; wrapper options go before `--`. For example, enable the additional heap analysis tools: ```powershell uvx chrome-devtools-mcp-wrapper -- npx -y chrome-devtools-mcp@latest --browser-url={browser_url} --memory-debugging ``` Use `chrome-devtools-mcp@1.10.1` in place of `@latest` to pin the verified release. Official Node.js requirements are `^20.19.0 || ^22.12.0 || >=23`. If live discovery fails, default configurations can use the bundled snapshot. For custom tool settings, JSON config files, or a different pinned upstream version, the wrapper requests the rea…
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.