66ced457d1
chore(main): release chrome-devtools-mcp 0.21.0 ( #1215 )
...
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.21.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.20.3...chrome-devtools-mcp-v0.21.0 )
(2026-04-01)
### 🎉 Features
* add a skill for detecting memory leaks using take_memory_snapshot tool
([#1162 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1162 ))
([d19a235https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d19a2350f975ec2fbf8ee61b35163a48c0146c32 ))
### 🛠️ Fixes
* **cli:** avoid defaulting to isolated when userDataDir is provided
([#1258 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1258 ))
([73e1e24https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/73e1e24b26f9e42a83116b586e34d47276a6a2fa ))
* list_pages should work after selected page is closed
([#1145 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1145 ))
([2664455https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/26644553028d8404fd65a005ea9c19a278671f4d ))
* mark lighthouse and memory as non-read-only
([#1769 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1769 ))
([bec9daehttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/bec9dae2d26b728feedcd660189f386e6228f3ae ))
* **telemetry:** record client name
([9a47b65https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/9a47b657d7b17b9bc64508530c93d55e8033e2a6 ))
* versioning for Claude Code plugin
([#1233 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1233 ))
([966b86fhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/966b86f3aaa9f87c2599b954c4e7f990c2a697ea ))
* wrap .mcp.json config in mcpServers key
([#1246 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1246 ))
([c7948cfhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/c7948cf0621d80b080220d4cfd36b62bef2790b9 ))
### 📄 Documentation
* Command Code CLI instructions for MCP server
([0a7c0a7https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0a7c0a74b471935a3e2f5ca0fd93556e8e5165ec ))
* provide disclaimer about supported browsers
([#1237 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1237 ))
([8676b72https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/8676b7216c66dfd323c2f6c272544a75dbab4dba ))
### 🏗️ Refactor
* set process titles for easier debugging
([#1770 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1770 ))
([0fe3896https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0fe3896d85c74ce8b2dc189fe8a310727f795344 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
---------
Co-authored-by: Alex Rudenko <alexrudenko@chromium.org >
2026-04-01 08:35:18 +00:00
2e1eabac02
chore: add eslint rule to validate tool schema patterns ( #1191 )
...
## Summary
- Add `@local/no-zod-nullable-object` ESLint rule that disallows
`.nullable()` and `.object()` usage in tool schema files
(`src/tools/**/*.ts`)
- Fix the existing `zod.object()` violation in `fill_form` by converting
the elements array from objects to `"uid=value"` formatted strings
- Remove the TODO from CONTRIBUTING.md and link the rule name to the
documented restriction
## Context
Per the [PR #1073
review](https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1073#discussion_r2872188785 )
and the CONTRIBUTING.md guidelines, tool schemas should not use
`.nullable()` or `.object()` types. Complex objects should be
represented as short formatted strings instead.
The rule catches:
- `zod.object({...})` / `z.object({...})` - flags direct zod object
schema usage
- `.nullable()` - flags nullable schema usage on any expression
Closes #1076
## Test plan
- [ ] `npx eslint src/tools/` passes with no violations
- [ ] Creating a test file with `zod.object()` or `.nullable()` in
`src/tools/` triggers the rule
- [ ] TypeScript compilation passes (`npx tsc --noEmit`)
- [ ] Existing `fill_form` test updated to use new string format
---------
Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com >
Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com >
Co-authored-by: Nikolay Vitkov <34244704+Lightning00Blade@users.noreply.github.com >
Co-authored-by: Alex Rudenko <alexrudenko@chromium.org >
2026-04-01 07:40:32 +00:00
73e1e24b26
fix(cli): avoid defaulting to isolated when userDataDir is provided ( #1258 )
...
## Summary
Fix `chrome-devtools start` so it no longer implicitly enables
`isolated` when `--userDataDir` is provided.
Previously, the CLI wrapper always defaulted `isolated` to `true` for
`start`, which caused `userDataDir` and `isolated` to conflict even when
the user only specified `--userDataDir`. This made it impossible to
start the CLI daemon against a persistent browser profile.
## Changes
- Update `chrome-devtools start` default handling in
`src/bin/chrome-devtools.ts`
- only default `isolated=true` when `userDataDir` is not set
- Clarify the `isolated` CLI description to document the conditional
default
- Update `docs/cli.md` to reflect that:
- `headless` is enabled by default
- `isolated` is enabled by default unless `--userDataDir` is provided
- Fix a small error message typo
## Why
This matches the intended semantics of the flags:
- `--isolated` means use a temporary user data dir
- `--userDataDir` means use a persistent, explicit user data dir
If the user passes `--userDataDir`, the CLI should not also implicitly
enable `isolated`.
## Testing
- Ran:
- `npm test -- tests/cli.test.ts`
- `npm test -- tests/e2e/chrome-devtools.test.ts`
Added an e2e regression test in `tests/e2e/chrome-devtools.test.ts` to
verify that:
- `chrome-devtools start --userDataDir <temp dir>` succeeds
- the CLI no longer fails with `Arguments userDataDir and isolated are
mutually exclusive`
- the daemon starts successfully when `userDataDir` is provided
2026-04-01 05:51:40 +00:00
4637ab9389
chore: Add execute_in_page_tool tool ( #1766 )
...
This allows the MCP server to call the in-page tools provided by the
inspected page.
Handling of (non-serializable) DOM elements as tool parameters or tool
output will be added in follow-ups.
2026-03-31 19:01:47 +00:00
44e511f6f6
chore: add function to sanitize params for tool calls ( #1250 )
...
This adds functions to sanitize the tool call parameters. They are not
called as of now since we don't have server side changes landed yet to
support these.
2026-03-31 17:56:43 +00:00
e513db184d
chore: improve take_memory_snapshot tool description ( #1774 )
...
I spotted a missing verb while looking at [the tool
reference](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md#take_memory_snapshot )
and decided to tweak the description a bit. WDYT?
2026-03-31 13:01:07 +00:00
604c41167b
chore(deps): bump lighthouse ( #1776 )
2026-03-31 12:17:44 +00:00
0fe3896d85
refactor: set process titles for easier debugging ( #1770 )
...
Refs https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1765
2026-03-31 10:42:26 +00:00
bec9dae2d2
fix: mark lighthouse and memory as non-read-only ( #1769 )
...
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1767
2026-03-31 10:39:15 +00:00
2eec55abbb
chore: edit punctuation in comment ( #1771 )
...
Reverts ChromeDevTools/chrome-devtools-mcp#1764
The goal is to trigger another run of release-please. The [previous
run](https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1215 )
did not pick up updated PR titles, so now I have updated PR descriptions
[(1)](https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1239 )[(2)](https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1762 )
in the hope that this causes the appropriate update in the release PR.
2026-03-31 06:51:54 +00:00
a10f591499
chore: edit punctuation in comment ( #1764 )
...
Only to trigger release-please
2026-03-31 05:54:29 +00:00
f7ae9e86ec
feat: Add list of in-page tools to responses for navigate_page, list_pages, select_page, close_page, new_page ( #1762 )
...
There is no mechanism which would allow a page to push an updated list
of in-page tools to the MCP server. The next best thing I can think of
is to append an updated list of in-page tools to the response for each
tool call related to page navigation (navigate_page, list_pages,
select_page, close_page, new_page).
2026-03-30 14:02:45 +00:00
cea963be68
feat: Add a new tool for listing in-page tools (gated behind a command line flag) ( #1239 )
...
This adds a `list_in_page_tools` MCP tool. When called, it dispatches a
`devtoolstooldiscovery` event on the active page. The page announces its
exposing tools by calling the event's `respondWith` method, which causes
the exposed tools to be stashed on the page's `window` object. This list
of in-page tools is then appended to the `list_in_page_tools` response.
Calling the exposed in-page tools from the MCP server will be handled in
a follow-up.
2026-03-30 09:51:35 +00:00
2664455302
fix: list_pages should work after selected page is closed ( #1145 )
...
## Problem
After closing the currently selected page, calling `list_pages` throws
an error:
```
The selected page has been closed. Call list_pages to see open pages.
```
This creates a deadlock: the error message tells users to call
`list_pages`, but `list_pages` itself throws the same error.
## Root Cause
`list_pages` is defined with `definePageTool`, which marks it as
`pageScoped: true`. The handler dispatch in `index.ts` (line ~186) calls
`context.getSelectedMcpPage()` for all page-scoped tools **before**
invoking the handler. When the selected page is closed,
`getSelectedPptrPage()` throws.
However, `list_pages` doesn't actually use the `page` parameter — its
handler only calls `response.setIncludePages(true)`.
## Fix
Change `list_pages` from `definePageTool` to `defineTool`. This bypasses
the page-scoped check while preserving all existing behavior since the
handler never used the page reference.
## Testing
Reproduced the issue following the steps in #1138 :
1. Call `list_pages` → returns page list ✅
2. Close the selected page
3. Call `list_pages` → now returns updated page list instead of throwing
✅
Fixes #1138
---------
Co-authored-by: Piotr Paulski <piotrpaulski@chromium.org >
2026-03-30 08:42:39 +00:00
e8e33d4172
chore: fix some typos ( #1240 )
2026-03-26 13:56:59 +00:00
b2b5e3fef6
chore: handling more client name enums ( #1228 )
...
The openclaw client name is defined at
https://github.com/openclaw/openclaw/blob/ea476de1e488979a3e9e5bf32e4d4f20e563144f/src/browser/chrome-mcp.ts#L234C14-L234C29
2026-03-24 18:18:14 +00:00
9a47b657d7
feat: record client name in telemetry. ( #1208 )
...
The changes in the PR intercepts the name of the MCP client right after
server initialization, coverts it into one of the existing enum values,
and append it with the telemetry request.
Note that the client name is unset if there is no client connected yet.
This means the server_start event won't have a client name.
Tested with gemini-cli.
---------
Co-authored-by: Yulun Zeng <yulunz@chromium.org >
2026-03-21 00:09:14 +00:00
350f7de66d
chore(main): release chrome-devtools-mcp 0.20.3 ( #1203 )
...
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.20.3](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.20.2...chrome-devtools-mcp-v0.20.3 )
(2026-03-20)
### 🛠️ Fixes
* mark categoryExtensions flag mutually exclusive with autoConnect
([#1202 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1202 ))
([8c2a7fchttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/8c2a7fc21ead6091567e85608f7916c001ccc7db )),
closes
[#1072 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1072 )
### ⚡ Performance
* **memory:** release old navigation request in NetworkCollector
([#1200 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1200 ))
([1e6456chttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/1e6456ce222a8f392341a530b2340336c7a1ab02 ))
* use CDP to find open DevTools pages (reland)
([#1210 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1210 ))
([53483bchttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/53483bc637566658754d781d88f4353ad47f44a7 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2026-03-20 16:11:07 +00:00
e56d79393c
chore: don't re-export internals ( #1211 )
2026-03-20 13:15:06 +00:00
53483bc637
perf: use CDP to find open DevTools pages (reland) ( #1210 )
...
This should reduce the flakiness and issue with finding open DevTools
tabs for the corresponding pages.
Currently we do multiple loops over all the targets, so this should have
a nice performance improvement when multiple pages are opened.
With a fallback for older versions.
2026-03-20 11:50:27 +00:00
1e6456ce22
perf(memory): release old navigation request in NetworkCollector ( #1200 )
...
Issue #1192
## Problem
In `--autoConnect` mode, `chrome-devtools-mcp` experiences a severe
memory leak (~13 MB/min) when Chrome is actively used. This eventually
leads to OOM crashes or kernel panics.
The root cause is in `src/PageCollector.ts`:
1. `NetworkCollector` overrides `splitAfterNavigation` but forgets to
call `navigations.splice(this.#maxNavigationSaved)`, causing the array
of navigations to grow infinitely.
2. Even within a single navigation (e.g., in long-lived SPA
applications), the `navigations[0]` array grows infinitely because there
is no limit on the number of items collected per navigation. Since
`HTTPRequest` objects are heavy, this quickly exhausts memory.
## Solution
1. Changed `#maxNavigationSaved` to `protected maxNavigationSaved` so
subclasses can access it.
2. Added `navigations.splice(this.maxNavigationSaved)` to
`NetworkCollector.splitAfterNavigation` to ensure old navigations are
properly discarded.
3. Introduced `protected maxItemsPerNavigation = 5000` to limit the
number of items stored per navigation. When the limit is reached, the
oldest item is removed (`shift()`), preventing unbounded memory growth
in SPAs.
Tested locally by running `npm run build` and verifying the fix.
---------
Co-authored-by: Wolfgang Beyer <woolfi.b@gmail.com >
2026-03-20 11:02:10 +00:00
8c2a7fc21e
fix: mark categoryExtensions flag mutually exclusive with autoConnect ( #1202 )
...
Fixes #1072
2026-03-18 16:57:30 +00:00
6279177016
chore(main): release chrome-devtools-mcp 0.20.2 ( #1199 )
...
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.20.2](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.20.1...chrome-devtools-mcp-v0.20.2 )
(2026-03-18)
### 📄 Documentation
* add troubleshooting for Claude Code plugin HTTPS clone failures
([#1195 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1195 ))
([d082ca4https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d082ca4ecd35a023d09f9c1ff949d5fb0c3fb069 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2026-03-18 11:39:17 +00:00
b14d03a655
revert: Reverts "perf: use CDP to find open DevTools pages." ( #1201 )
...
Reverts ChromeDevTools/chrome-devtools-mcp#1150
Quick revert because this change has broken debugging of Electron apps.
2026-03-18 10:46:24 +00:00
e237bade38
chore(main): release chrome-devtools-mcp 0.20.1 ( #1163 )
...
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.20.1](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.20.0...chrome-devtools-mcp-v0.20.1 )
(2026-03-16)
### 🛠️ Fixes
* update VS Code manual installation powershell command
([#1151 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1151 ))
([6c64a5bhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/6c64a5b543714796b25a12dc6f2be7a1e683e8bd ))
### ⚡ Performance
* use CDP to find open DevTools pages.
([#1150 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1150 ))
([94de19chttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/94de19cdcdae9e31d0962b273ce352dc248eb5a8 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2026-03-17 09:39:16 +00:00
94de19cdcd
perf: use CDP to find open DevTools pages. ( #1150 )
...
This should reduce the flakiness and issue with finding open DevTools
tabs for the corresponding pages.
Currently we do multiple loops over all the targets, so this should have
a nice performance improvement when multiple pages are opened.
2026-03-11 13:30:30 +00:00
8b7d22f76d
chore(main): release chrome-devtools-mcp 0.20.0 ( #1126 )
...
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.20.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.19.0...chrome-devtools-mcp-v0.20.0 )
(2026-03-11)
### 🎉 Features
* experimental `chrome-devtools` CLI
([#1100 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1100 ))
([1ac574ehttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/1ac574e7154948e86e414e5149fb975a190d5bb0 ))
### 📄 Documentation
* fix typo
([#1155 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1155 ))
([b59cabchttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/b59cabcc1d59802ffd7d9667040188e46192357d ))
* fix typos and improve phrasing
([#1130 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1130 ))
([70d4f36https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/70d4f365dc619a5743e697c30800f7065bc6227d ))
* revise contribution process and add release process
([#1134 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1134 ))
([d7d26a1https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d7d26a103b840e2feb7cb9af6a242edda94f1ddf ))
* **troubleshooting:** add symptom for missing tools due to read-only
mode
([#1148 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1148 ))
([57e7d51https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/57e7d51e8ca1e2ee325a9e7a9c64c033acbe6d6a ))
* Update troubleshooting for MCP server connection errors
([#1017 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1017 ))
([00f9c31https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/00f9c3108ab9caefca57998439052c728298920b ))
### 🏗️ Refactor
* move main files
([#1120 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1120 ))
([c2d8009https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/c2d8009ff75f76bce1ec4cf79c2467b50d81725e ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2026-03-11 10:36:28 +00:00
06c295278d
chore: work around the SDK's MCP client issues ( #1137 )
...
MCP SDK client does not set windowsHide when spawning the process unless
it is on windows under Electron (not sure why). But I think we can
safely pretend to be "electron".
Refs https://github.com/modelcontextprotocol/typescript-sdk/issues/1638
Refs https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1100
2026-03-06 14:15:14 +00:00
1c6db83810
chore: use windowsHide in daemon client ( #1135 )
...
prevents cmd.exe from showing on Windows.
2026-03-06 08:45:51 +00:00
f07353f88a
chore: report current cli args ( #1133 )
...
This CL records the args in the daemon and reports them back to the
client via the status call.
2026-03-06 08:23:35 +00:00
ae311fc23c
chore: filter out some tools from CLI ( #1131 )
...
Filters out wait_for and fill_form.
2026-03-06 08:05:50 +00:00
c2d8009ff7
refactor: move main files ( #1120 )
...
- `chrome-devtools-mcp.js` is the `npx chrome-devtools-mcp`
- `chrome-devtools.js` is the new CLI
- `-cli-options.js` is the corresponding options
- all these files are in the bin folder to indicate they are executable
2026-03-05 21:51:37 +00:00
2a6ac709ea
chore: extension pages list ( #1065 )
...
This PR introduces extension pages in the listPages tool under the flag
--category-extension.
2026-03-05 20:57:07 +00:00
8388be52bd
chore(main): release chrome-devtools-mcp 0.19.0 ( #1125 )
...
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.19.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.18.1...chrome-devtools-mcp-v0.19.0 )
(2026-03-05)
### 🎉 Features
* add pageId routing for parallel multi-agent workflows
([#1022 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1022 ))
([caf601ahttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/caf601a32832bb87cfac801a6bbeacb87508412f )),
closes
[#1019 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1019 )
* Add skill which helps with onboarding of the mcp server
([#1083 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1083 ))
([7273f16https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/7273f16ec08f6d5b46a2693b0ad4d559086ded89 ))
* integrate Lighthouse audits
([#831 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/831 ))
([dfdac26https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/dfdac2648e560d756a8711ad3bb1fa470be8e7c9 ))
### 🛠️ Fixes
* improve error messages around --auto-connect
([#1075 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1075 ))
([bcb852dhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/bcb852dd2e440b0005f4a9ad270a1a7998767907 ))
* improve tool descriptions
([#965 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/965 ))
([bdbbc84https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/bdbbc84c125bdd48f4be48aa476bec0323de611c ))
* repair broken markdown and extract snippets in a11y-debugging skill
([#1096 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1096 ))
([adac7c5https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/adac7c537ee304f324c5e7284fb363396d1773f5 ))
* simplify emulation and script tools
([#1073 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1073 ))
([e51ba47https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/e51ba4720338951e621585b77efc6a0e07678d99 ))
* simplify focus state management
([#1063 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1063 ))
([f763da2https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/f763da24a10e27605c0a5069853ce7c92974eec2 ))
* tweak lighthouse description
([#1112 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1112 ))
([5538180https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/55381804ae7ffa8a1e5933b621a9b8390b3000ff ))
### 📄 Documentation
* Adapt a11y skill to utilize Lighthouse
([#1054 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1054 ))
([21634e6https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/21634e660c346e469ae62116b1824538f51567dd ))
* add feature release checklist to CONTRIBUTING.md
([#1118 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1118 ))
([0378457https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/03784577ffb6e238bcb2d637bff9ad759723ea7b ))
* fix typo in README regarding slim mode
([#1093 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1093 ))
([92f2c7bhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/92f2c7b48b56a6b1d6ac7c9e2f2e92beb26bcf62 ))
### 🏗️ Refactor
* clean up more of the context getters
([#1062 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1062 ))
([9628dabhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/9628dabcb4d39f0b94d152a0fc419e049246a29d ))
* consistently use McpPage in tools
([#1057 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1057 ))
([302e5a0https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/302e5a04191ba0558e3c79f1486d01d5eb0f6896 ))
* improve type safety for page scoped tools
([#1051 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1051 ))
([5f694c6https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/5f694c60ffd21f8b022554c92b2ad4cbdb457375 ))
* make cdp resolvers use McpPage
([#1060 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1060 ))
([d6c06c5https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d6c06c56a7b8e4968318adc9fc7c820ace9f5bd9 ))
* move dialog handling to McpPage
([#1059 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1059 ))
([40c241bhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/40c241bbfc80d6282953ab325b30a597d3d85ade ))
* move server to a separate file
([#1043 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1043 ))
([a8bf3e5https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/a8bf3e585682c3126dfd378e9f98b5dc7ab6045d ))
* remove page passing via context
([#1061 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1061 ))
([4cb5a17https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/4cb5a17b57f57d8a367cd423c960ba122b9952e3 ))
* set defaults to performance trace tool
([#1090 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1090 ))
([dfa9b79https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/dfa9b79a4ecc9e67f5b043f2dd97f6889d1fee0b ))
* simplify the response texts
([#1095 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1095 ))
([cb0079ehttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/cb0079efbbd41874f6913772fe3f2a037e9f5f8f ))
* type-cast as internal CdpPage interface
([#1064 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/1064 ))
([2d5e4fahttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/2d5e4fa3579650a384ff21c88c2e6b9cda031e1a ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2026-03-05 19:23:28 +01:00
013110b0ee
chore: generate cli automatically ( #1117 )
2026-03-05 13:35:15 +00:00
4e4038beff
chore: configure cli args ( #1115 )
...
This PR configures CLI args for the start command. It removes arguments
that do not make sense.
2026-03-05 12:48:42 +00:00
dc53fa331d
chore: validate start args ( #1113 )
...
The `start` command accepts the MCP server CLI options. This PR adds
yargs validation to the start command and re-uses the same yargs
definitions.
2026-03-05 11:27:26 +01:00
55381804ae
fix: tweak lighthouse description ( #1112 )
2026-03-05 09:12:45 +00:00
d95e9ba89d
chore: add detailed daemon status ( #1110 )
...
adds additional details about running daemon.
2026-03-05 08:41:10 +00:00
88da3b83da
chore: fix bundling for the CLI ( #1111 )
...
extracts non-launch related fixes from
https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1100
2026-03-05 08:26:37 +00:00
bad5a16f95
chore: handle images in the CLI ( #1107 )
...
- save base64 data as an image to a tmp file.
- change `--format` to `--output-format` to avoid conflicts.
2026-03-05 07:49:13 +00:00
bdbbc84c12
fix: improve tool descriptions ( #965 )
...
Addresses cases where DevTools MCP tools were not consistently picked up
from natural language prompts by improving tool descriptions and
metadata.
Validation:
Tested locally across multiple prompts related to LCP and page
performance.
MCP tools were selected more consistently after the description updates.
Refs #940
---------
Signed-off-by: dependabot[bot] <support@github.com >
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com >
Co-authored-by: Nikolay Vitkov <34244704+Lightning00Blade@users.noreply.github.com >
Co-authored-by: Alex Rudenko <alexrudenko@chromium.org >
2026-03-05 06:47:15 +00:00
a02a5671f9
chore: change text format to md in CLI ( #1102 )
...
as it is closer to reality.
2026-03-04 18:08:50 +00:00
a073c0c54b
chore(deps-dev): bump puppeteer from 24.37.5 to 24.38.0 in the bundled group ( #1099 )
...
Bumps the bundled group with 1 update:
[puppeteer](https://github.com/puppeteer/puppeteer ).
Updates `puppeteer` from 24.37.5 to 24.38.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/puppeteer/puppeteer/releases ">puppeteer's
releases</a>.</em></p>
<blockquote>
<h2>puppeteer-core: v24.38.0</h2>
<h2><a
href="https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v24.37.5...puppeteer-core-v24.38.0 ">24.38.0</a>
(2026-03-04)</h2>
<h3>🎉 Features</h3>
<ul>
<li>roll to Chrome 146.0.7680.31 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14729 ">#14729</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/627eb5e6572f5248286ab09d74c204e2399632e8 ">627eb5e</a>)</li>
<li>roll to Firefox 148.0 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14728 ">#14728</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/09b655a1a4b2ee389f4a63f701a347566a5b9d88 ">09b655a</a>)</li>
</ul>
<h3>🛠️ Fixes</h3>
<ul>
<li>consider browsingContext.navigationCommitted to dispose an existing
navigation (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14724 ">#14724</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/b4e92c637c503710895c842f391793018c4f35b5 ">b4e92c6</a>)</li>
<li>disable PartitionAllocSchedulerLoopQuarantineTaskControlledPurge (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14744 ">#14744</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/e6c7425d3f459adfbf5c1dd0b230da33fa9eb7c3 ">e6c7425</a>)</li>
<li>roll to Chrome 145.0.7632.117 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14719 ">#14719</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/1d407e1e69ee0f307f8819152a980fa0a24835ff ">1d407e1</a>)</li>
</ul>
<h2>puppeteer: v24.38.0</h2>
<h2><a
href="https://github.com/puppeteer/puppeteer/compare/puppeteer-v24.37.5...puppeteer-v24.38.0 ">24.38.0</a>
(2026-03-04)</h2>
<h3>🎉 Features</h3>
<ul>
<li>roll to Chrome 146.0.7680.31 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14729 ">#14729</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/627eb5e6572f5248286ab09d74c204e2399632e8 ">627eb5e</a>)</li>
</ul>
<h3>Dependencies</h3>
<ul>
<li>The following workspace dependencies were updated
<ul>
<li>dependencies
<ul>
<li>puppeteer-core bumped from 24.37.5 to 24.38.0</li>
</ul>
</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/puppeteer/puppeteer/blob/main/CHANGELOG.md ">puppeteer's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/puppeteer/puppeteer/compare/puppeteer-v24.37.5...puppeteer-v24.38.0 ">24.38.0</a>
(2026-03-04)</h2>
<h3>🎉 Features</h3>
<ul>
<li>roll to Chrome 146.0.7680.31 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14729 ">#14729</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/627eb5e6572f5248286ab09d74c204e2399632e8 ">627eb5e</a>)</li>
<li>roll to Firefox 148.0 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14728 ">#14728</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/09b655a1a4b2ee389f4a63f701a347566a5b9d88 ">09b655a</a>)</li>
</ul>
<h3>Dependencies</h3>
<ul>
<li>The following workspace dependencies were updated
<ul>
<li>dependencies
<ul>
<li>puppeteer-core bumped from 24.37.5 to 24.38.0</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3>🛠️ Fixes</h3>
<ul>
<li>consider browsingContext.navigationCommitted to dispose an existing
navigation (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14724 ">#14724</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/b4e92c637c503710895c842f391793018c4f35b5 ">b4e92c6</a>)</li>
<li>disable PartitionAllocSchedulerLoopQuarantineTaskControlledPurge (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14744 ">#14744</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/e6c7425d3f459adfbf5c1dd0b230da33fa9eb7c3 ">e6c7425</a>)</li>
<li>roll to Chrome 145.0.7632.117 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14719 ">#14719</a>)
(<a
href="https://github.com/puppeteer/puppeteer/commit/1d407e1e69ee0f307f8819152a980fa0a24835ff ">1d407e1</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/d3356fac46478974c5b88ba2b26b26954cb741ff "><code>d3356fa</code></a>
chore: release main (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14720 ">#14720</a>)</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/e6c7425d3f459adfbf5c1dd0b230da33fa9eb7c3 "><code>e6c7425</code></a>
fix: disable PartitionAllocSchedulerLoopQuarantineTaskControlledPurge
(<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14744 ">#14744</a>)</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/e24f43290280df6398e992842490631aafd9f287 "><code>e24f432</code></a>
chore(deps-dev): bump the dev-dependencies group across 1 directory with
7 up...</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/b12fca9bd9bedb9c90863c52e7359cfbf281a81e "><code>b12fca9</code></a>
test: update tests and add diagnostics (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14741 ">#14741</a>)</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/627eb5e6572f5248286ab09d74c204e2399632e8 "><code>627eb5e</code></a>
feat: roll to Chrome 146.0.7680.31 (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14729 ">#14729</a>)</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/e0e3e89aa4d7e1825d411a4729a76a0852824c83 "><code>e0e3e89</code></a>
chore: enable blank issues in issue template configuration (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14739 ">#14739</a>)</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/ba19944981f4e601127a5b7b54feefd1df972cbe "><code>ba19944</code></a>
chore(deps-dev): bump rollup from 4.22.4 to 4.59.0 in
/examples/puppeteer-in-...</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/b4e92c637c503710895c842f391793018c4f35b5 "><code>b4e92c6</code></a>
fix: consider browsingContext.navigationCommitted to dispose an existing
navi...</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/57b40c03e11ec5defebfa30cb9fcea5d6f6ae572 "><code>57b40c0</code></a>
chore(deps): bump typed-query-selector from 2.12.0 to 2.12.1 in the
dependenc...</li>
<li><a
href="https://github.com/puppeteer/puppeteer/commit/eca8ca4b90c9e16a86152a62ed8839119c4386a3 "><code>eca8ca4</code></a>
chore(deps): bump the all group in /website with 2 updates (<a
href="https://redirect.github.com/puppeteer/puppeteer/issues/14732 ">#14732</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/puppeteer/puppeteer/compare/puppeteer-v24.37.5...puppeteer-v24.38.0 ">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores )
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
</details>
---------
Signed-off-by: dependabot[bot] <support@github.com >
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alex Rudenko <alexrudenko@chromium.org >
2026-03-04 15:58:19 +00:00
9d14d7ad11
chore: shim puppeteer in lh bundle ( #1101 )
...
LH PR https://github.com/GoogleChrome/lighthouse/pull/16895 Contains
unmodified output from `npm run update-lighthouse`.
2026-03-04 15:49:14 +00:00
cb0079efbb
refactor: simplify the response texts ( #1095 )
...
- removed redundant headers in Markdown
- updates more tests to use snapshots
2026-03-04 07:23:37 +00:00
dfa9b79a4e
refactor: set defaults to performance trace tool ( #1090 )
...
Defaults make it easier to use.
2026-03-04 07:04:12 +00:00
79337ec71a
chore: tweak CLI ( #1088 )
...
- document optional params
- remove customHelp
2026-03-03 20:02:07 +00:00
baa80f951a
chore: add via CLI flag ( #1086 )
...
This is used for usage stats.
2026-03-03 20:00:02 +00:00
109bf43e4c
chore: fix arg forwarding in CLI ( #1084 )
...
Drive-by: e2e tests for major scenarios.
Drive-by: make stopDaemon more robust.
2026-03-03 17:47:01 +00:00
browser-automation-bot