347768d11c
chore(main): release chrome-devtools-mcp 0.3.0 ( #138 )
...
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.3.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.7...chrome-devtools-mcp-v0.3.0 )
(2025-09-25)
### Features
* Add pagination list_network_requests
([#145 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/145 ))
([4c909bbhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/4c909bb8d7c4a420cb8e3219ec98abf28f5cc664 ))
### Bug Fixes
* avoid reporting page close errors as errors
([#127 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/127 ))
([44cfc8fhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/44cfc8f945edf9370efe26247f322a59a4a4a7be ))
* clarify the node version message
([#135 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/135 ))
([0cc907ahttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0cc907a9ad79289a6785e9690c3c6940f0a5de52 ))
* do not set channel if executablePath is provided
([#150 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/150 ))
([03b59f0https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/03b59f0bca024173ad45d7a617994e919d9cbbad ))
* **performance:** ImageDelivery insight errors
([#144 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/144 ))
([d64ba0dhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d64ba0d9027540eb707381e2577ae3c1fe014346 ))
* roll latest DevTools to handle Insight errors
([#149 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/149 ))
([b2e1e39https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/b2e1e3944c7fa170584ce36c7b8923b0e6d6c6cb ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-25 18:51:31 +02:00
03b59f0bca
fix: do not set channel if executablePath is provided ( #150 )
...
Fixes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/148
2025-09-25 18:44:31 +02:00
b2e1e3944c
fix: roll latest DevTools to handle Insight errors ( #149 )
...
This commit updates DevTools to the latest release. This most
importantly includes a fix for #124 and other reported issues where
Insights that were actually errors were not handled correctly. They are
now formatted correctly on the DevTools side and now will not break
performance traces in the MCP server.
2025-09-25 18:25:35 +02:00
15277541d8
chore: add additional EsLint rule ( #147 )
2025-09-25 17:20:01 +02:00
4c909bb8d7
feat: Add pagination list_network_requests ( #145 )
...
## Summary
This PR enhances the `list_network_requests` tool with pagination
support to handle large numbers of network requests efficiently. See
[this
issue](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/136 ).
## Motivation
In my experience, the `list_network_requests` tool frequently hits LLM
token limits on pages with many requests, making it unusable for modern
web applications. I wanted to add pagination to allow agents to be more
flexible and manage token limits on their own.
## Changes
### Pagination Support
- Added `pageSize` parameter to limit requests per call
- Added `pageToken` parameter for navigation between pages
- Added pagination metadata in responses (nextPageToken,
previousPageToken, startIndex, endIndex, total)
### Implementation Details
- **New utility**: `src/utils/pagination.ts` - generic pagination
function
- **Enhanced McpResponse**: Added pagination options to
`setIncludeNetworkRequests()`
- **Updated network tool**: Added pagination parameters to schema
- **Offset-based pagination**: Uses numeric tokens, handles invalid
tokens gracefully
## Testing
- Comprehensive test coverage for pagination scenarios
- Tests for first page, subsequent pages, invalid tokens, and edge cases
- All existing tests continue to pass
## Backward Compatibility
- If no pagination parameters are provided, the MCP will return all
requests (same as before)
2025-09-25 16:26:43 +02:00
d64ba0d902
fix(performance): ImageDelivery insight errors ( #144 )
...
This fixes the ImageDelivery insight which throws when we try to
generate it
because of its dependency on core/i18n. The long term fix here is to
remove the reliance of models/trace on the core/i18n package, or at
least dependency inject it, but this is a quick fix to at least make
this insight available.
The irony is that we don't even use the string in the AI output; but if
we don't have the method available we cannot generate the insight.
This fixes part of #124 by making this insight not error. The other
required work for that bug is to deal with Insights that do error. That
work is done in DevTools, but we need to ship & roll a new version into
the MCP server.
2025-09-25 13:38:52 +02:00
44cfc8f945
fix: avoid reporting page close errors as errors ( #127 )
...
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/125
2025-09-25 10:40:51 +00:00
b3daa4899b
docs: add JetBrains AI Assistant and Junie ( #126 )
...
JetBrains AI Assistant and Junie also support MCP, this PR describes the
necessary configuration.
---------
Co-authored-by: Sebastian Benz <sebastian.benz@gmail.com >
Co-authored-by: Sebastian Benz <sbenz@google.com >
2025-09-25 12:31:28 +02:00
5cfa7150fc
chore: latest gemini extension ( #142 )
2025-09-25 09:41:25 +00:00
0cc907a9ad
fix: clarify the node version message ( #135 )
2025-09-25 08:39:19 +02:00
3597a3b4cf
chore(deps): bump puppeteer ( #128 )
2025-09-24 21:35:08 +02:00
e5b6600022
docs: fix readme ( #122 )
...
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/119
2025-09-24 14:48:15 +00:00
2b315b78fc
chore: add npx command ( #120 )
2025-09-24 16:32:18 +02:00
b53f114738
chore: update gemini-extension.json ( #118 )
2025-09-24 14:13:23 +00:00
3181d704d4
chore(main): release chrome-devtools-mcp 0.2.7 ( #115 )
...
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.2.7](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.6...chrome-devtools-mcp-v0.2.7 )
(2025-09-24)
### Bug Fixes
* validate and report incompatible Node versions
([#113 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/113 ))
([adfcecfhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/adfcecf9871938b1ad5d1460e0050b849fb2aa49 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-24 14:55:21 +02:00
adfcecf987
fix: validate and report incompatible Node versions ( #113 )
...
Ref https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/92
2025-09-24 14:45:27 +02:00
c9fdd2ce12
chore: add gemini extension json ( #114 )
2025-09-24 14:38:37 +02:00
f2fe7f0e5e
test: add node23 to the matrix ( #100 )
2025-09-24 09:28:57 +00:00
26878222c9
chore(main): release chrome-devtools-mcp 0.2.6 ( #106 )
...
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.2.6](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.5...chrome-devtools-mcp-v0.2.6 )
(2025-09-24)
### Bug Fixes
* manually bump server.json versions based on package.json
([#105 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/105 ))
([cae1cf1https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/cae1cf13d5a97add3b96f20c425f720a1ceabf94 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-24 08:30:56 +00:00
cae1cf13d5
fix: manually bump server.json versions based on package.json ( #105 )
...
it appears that mcp registry publishing tools would not sync
automatically with package.json.
2025-09-24 10:23:06 +02:00
33e8662662
chore(main): release chrome-devtools-mcp 0.2.5 ( #104 )
...
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.2.5](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.4...chrome-devtools-mcp-v0.2.5 )
(2025-09-24)
### Bug Fixes
* add mcpName to package.json
([#103 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/103 ))
([bd0351fhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/bd0351fd36ae35e41e613f0d15df40aeca17ba94 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-24 10:02:12 +02:00
bd0351fd36
fix: add mcpName to package.json ( #103 )
2025-09-24 07:59:37 +00:00
901a730ed9
chore(main): release chrome-devtools-mcp 0.2.4 ( #102 )
...
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.2.4](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.3...chrome-devtools-mcp-v0.2.4 )
(2025-09-24)
### Bug Fixes
* forbid closing the last page
([#90 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/90 ))
([0ca2434https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0ca2434a29eb4bc6e570a4ebe21a135d85f4c0f3 ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-24 09:52:42 +02:00
0ca2434a29
fix: forbid closing the last page ( #90 )
...
McpContext currently assumes that there is a page. Eventually we might
support closing the browser by closing the last page but right now we do
not really have responses that indicate that the browser was closed. So
this PR helps the LLM understand that it is okay to keep the last page
running (and there are platform-specific differences as to what happens
if the last page is closed).
Ref https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/87
2025-09-24 07:23:53 +00:00
2ee30bf37b
chore: latest mcp registry schema ( #101 )
2025-09-24 07:21:36 +00:00
64c446f7b2
chore(main): release chrome-devtools-mcp 0.2.3 ( #85 )
...
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.2.3](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.2...chrome-devtools-mcp-v0.2.3 )
(2025-09-24)
### Bug Fixes
* add a message indicating that no console messages exist
([#91 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/91 ))
([1a4ba4dhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/1a4ba4d3e05f51a85747816f8638f31230881437 ))
* clean up pending promises on action errors
([#84 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/84 ))
([4e7001ahttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/4e7001ac375ec51f55b29e9faf68aff0dd09fa0f ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-24 07:08:12 +00:00
cb17ae80e6
docs: add Codex MCP configuration guide ( #95 )
...
Co-authored-by: Sebastian Benz <sbenz@google.com >
2025-09-24 08:48:06 +02:00
8d0cb79b50
chore: update mcp publisher ( #98 )
2025-09-24 06:20:17 +00:00
82bd72aef7
chore: fix label for feature request issues ( #97 )
2025-09-24 08:00:04 +02:00
1ed7e45fef
docs: explain when the browser starts ( #89 )
2025-09-23 20:13:03 +00:00
1a4ba4d3e0
fix: add a message indicating that no console messages exist ( #91 )
...
To avoid clients being confused about the lack of console messages.
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/87
2025-09-23 22:10:46 +02:00
4e7001ac37
fix: clean up pending promises on action errors ( #84 )
2025-09-23 18:33:50 +00:00
d622b9b37d
chore(main): release chrome-devtools-mcp 0.2.2 ( #76 )
...
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.2.2](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.1...chrome-devtools-mcp-v0.2.2 )
(2025-09-23)
### Bug Fixes
* cli version being reported as unknown
([#74 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/74 ))
([d6bab91https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d6bab912df55dc2e96a8d7893d1906f1fc608d0a ))
* remove unnecessary waiting for navigation
([#83 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/83 ))
([924c042https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/924c042492222a555074063841ce765342e3b5b9 ))
* rework performance parsing & error handling
([#75 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/75 ))
([e8fb30chttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/e8fb30c1bfdc2b4ea8c2daf74b24aa82210f99be ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-23 18:26:00 +00:00
924c042492
fix: remove unnecessary waiting for navigation ( #83 )
2025-09-23 18:23:53 +00:00
67af3fefe5
chore: publish to MCP registry ( #78 )
...
Includes server.json and the GitHub Actions steps.
2025-09-23 19:59:48 +02:00
9c8da4a449
test: use cft for e2e tests ( #80 )
...
we were using the Chrome version pre-installed on the GitHub actions and
I wonder if it could have been the source for the flakiness.
2025-09-23 19:53:33 +02:00
92046183d4
chore(deps): bump puppeteer ( #79 )
...
Contains fixes for the pipe transport.
2025-09-23 17:01:19 +00:00
74fa209145
test: skip flaky test ( #77 )
2025-09-23 14:03:44 +00:00
e8fb30c1bf
fix: rework performance parsing & error handling ( #75 )
...
This PR tidies up the code around performance parsing and what we
respond with from our tools. It introduces the ability to have no
Insights from a trace (relatively rare, but can happen), and also adds
more information to the output in the event that something went wrong.
Previously we just logged errors, but if we respond with them here that
will also help users report issues and increase the chances that we can
debug them.
2025-09-23 15:42:35 +02:00
d6bab912df
fix: cli version being reported as unknown ( #74 )
2025-09-23 13:33:18 +00:00
17edcd856d
chore(main): release chrome-devtools-mcp 0.2.1 ( #54 )
...
publish-on-tag / publish (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.2.1](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.2.0...chrome-devtools-mcp-v0.2.1 )
(2025-09-23)
### Bug Fixes
* add 'on the selected page' to performance tools
([#69 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/69 ))
([b877f7ahttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/b877f7a3053d0cdf2aad1fefc26cf7b913eb95ce ))
* **emulation:** correctly report info for selected page
([#63 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/63 ))
([1e8662fhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/1e8662f06860aecb5c01ed4ff1515ceb9dac26e4 ))
* expose timeout when Emulation is enabled
([#73 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/73 ))
([0208bfdhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0208bfdcf6924953879408c18f4c20da544bf4ff ))
* fix browserUrl not working
([#53 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/53 ))
([a6923b8https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/a6923b8d9397d12ee0f9fe67dd62b10088ec6e87 ))
* increase timeouts in case of Emulation
([#71 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/71 ))
([c509c64https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/c509c64576e1be1ddc283653004ef08a117907a2 ))
* **windows:** work around Chrome not reporting reasons for crash
([#64 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/64 ))
([d545741https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d5457412a4a76726547190fb3a46bb78c9d6645c ))
---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please ). See
[documentation](https://github.com/googleapis/release-please#release-please ).
2025-09-23 14:19:36 +02:00
0208bfdcf6
fix: expose timeout when Emulation is enabled ( #73 )
...
Co-authored-by: Alex Rudenko <OrKoN@users.noreply.github.com >
2025-09-23 11:17:53 +02:00
91d83c4190
test: fix shell for windows tests ( #72 )
2025-09-23 09:37:22 +02:00
c509c64576
fix: increase timeouts in case of Emulation ( #71 )
2025-09-22 18:13:49 +02:00
a9cf9d77f7
test: await dialog dismiss to prevent async activity errors ( #70 )
2025-09-22 17:11:04 +02:00
b877f7a305
fix: add 'on the selected page' to performance tools ( #69 )
...
To hopefully ensure the client makes sure to navigate to and select a
page before starting the trace.
Bug: 446171427
2025-09-22 17:03:26 +02:00
d5457412a4
fix(windows): work around Chrome not reporting reasons for crash ( #64 )
2025-09-22 16:40:56 +02:00
85a6d640f7
docs: small README wording tweaks ( #67 )
2025-09-22 14:38:58 +00:00
93923d9311
chore: add browser logs to the log file ( #66 )
2025-09-22 16:36:40 +02:00
bfbdada6c7
docs: document mcp client sandboxing ( #65 )
...
Co-authored-by: Sebastian Benz <sbenz@google.com >
2025-09-22 14:16:44 +00:00
browser-automation-bot