chrome-devtools-mcp adds Chrome extension debugging tools
Introduced 2026-04-21 · score 0.98
HOW TO USE IT
When debugging an unpacked Chrome extension, start chrome-devtools-mcp with the extensions category enabled, then install or inspect/manage the extension using its documented MCP tools. The extension tools require a pipe connection; autoConnect, browserUrl, and wsEndpoint are unsupported with this feature until Chrome 149 is released.
npx chrome-devtools-mcp@0.22.0 --category-extensions=trueinstall_extension({"path":"<absolute-path-to-unpacked-extension-folder>"})list_extensions({})
reload_extension({"id":"<extension-id>"})
trigger_extension_action({"id":"<extension-id>"})
uninstall_extension({"id":"<extension-id>"})WHY THIS HELPS
When debugging an unpacked Chrome extension, enable the extension tool category and use its tools to manage and inspect extensions.
REQUIREMENTS AND LIMITATIONS
- Version: 0.22.0
- --category-extensions / --categoryExtensions: Boolean; set true to include extension tools. Default false.
- install_extension.path (required): Absolute path to the unpacked extension folder.
- reload_extension.id (required): ID of the extension to reload.
- trigger_extension_action.id (required): ID of the extension whose default action to trigger.
- uninstall_extension.id (required): ID of the extension to uninstall.
- Prerequisite: Extension tools are inactive by default; enable them with --category-extensions=true.
- Prerequisite: This feature is supported only with a pipe connection. autoConnect, browserUrl, and wsEndpoint are unsupported until Chrome 149 is released.
- Extension tools are not active by default.
- This feature is currently only supported with a pipe connection.
- autoConnect, browserUrl, and wsEndpoint are not supported with this feature until 149 will be released.
- install_extension requires an absolute path to the unpacked extension folder.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v0.22.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1922
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/3ff21cf30dae19a6af85d836b1b55314f53ff401/README.md
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/3ff21cf30dae19a6af85d836b1b55314f53ff401/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON