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
1e8662f068
fix(emulation): correctly report info for selected page ( #63 )
...
Previously if one page was setting emulation all were reporting it.
2025-09-22 16:03:47 +02:00
54efe95620
chore: add provenance back ( #61 )
...
Reverts ChromeDevTools/chrome-devtools-mcp#49
2025-09-22 13:31:38 +00:00
699258accf
refactor: move WaitForHelper to class and use it from inside context ( #62 )
...
This does not change any behavior but only refactors the code so the
following changes are easier to seem
2025-09-22 15:29:30 +02:00
3f38bf10c9
chore: define es and lib requirements ( #60 )
2025-09-22 13:01:20 +02:00
8ce4888611
docs: improve Cursor install instructions ( #58 )
...
Adds an install to cursor button (also fixes windows support in docs
generation).
2025-09-22 09:35:07 +00:00
b830b436f9
chore: roll devtools-frontend and update snapshots ( #59 )
2025-09-22 09:29:21 +00:00
320314ea79
chore(deps): bump @modelcontextprotocol/sdk from 1.18.0 to 1.18.1 in the dependencies group ( #56 )
...
Bumps the dependencies group with 1 update:
[@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk ).
Updates `@modelcontextprotocol/sdk` from 1.18.0 to 1.18.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/modelcontextprotocol/typescript-sdk/releases "><code>@modelcontextprotocol/sdk</code>'s
releases</a>.</em></p>
<blockquote>
<h2>1.18.1</h2>
<h2>What's Changed</h2>
<ul>
<li>fix: prevent streamable http wite after end from crashing the node
process by <a href="https://github.com/MQ37 "><code>@MQ37</code></a> in
<a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/933 ">modelcontextprotocol/typescript-sdk#933</a></li>
<li>chore: update version to 1.18.1 for weekly release by <a
href="https://github.com/felixweinberger "><code>@felixweinberger</code></a>
in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/950 ">modelcontextprotocol/typescript-sdk#950</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/MQ37 "><code>@MQ37</code></a> made their
first contribution in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/933 ">modelcontextprotocol/typescript-sdk#933</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/modelcontextprotocol/typescript-sdk/compare/1.18.0...1.18.1 ">https://github.com/modelcontextprotocol/typescript-sdk/compare/1.18.0...1.18.1 </a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/modelcontextprotocol/typescript-sdk/commit/c94ba4b43cd305e39d88985c73d6b9bc1153da84 "><code>c94ba4b</code></a>
chore: update version to 1.18.1 for weekly release (<a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/950 ">#950</a>)</li>
<li><a
href="https://github.com/modelcontextprotocol/typescript-sdk/commit/24b3972931395c70358146b00fec809625a550f8 "><code>24b3972</code></a>
fix: prevent streamable http wite after end from crashing the node
process (#...</li>
<li>See full diff in <a
href="https://github.com/modelcontextprotocol/typescript-sdk/compare/1.18.0...1.18.1 ">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 merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@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>
2025-09-22 09:01:00 +02:00
0c7daa0b86
chore: refactor docs generating ( #55 )
...
* add script `npm run docs` that builds, generate docs and runs
formatter to auto fix formatting after doc generation
* rename generate-docs to docs:generate
* update presubmit workflow
* add docs process to contributing.md
2025-09-19 15:57:10 +02:00
a6923b8d93
fix: fix browserUrl not working ( #53 )
...
Setting the default channel in the CLI resulted in our mutually
exclusive check for browserUrl and channel to fail.
2025-09-19 12:24:05 +02:00
22755533b8
chore(main): release chrome-devtools-mcp 0.2.0 ( #50 )
...
publish-on-tag / publish (push) Has been cancelled
🤖 I have created a release *beep* *boop*
---
##
[0.2.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.1.0...chrome-devtools-mcp-v0.2.0 )
(2025-09-17)
### Features
* add performance_analyze_insight tool.
([#42 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/42 ))
([21e175bhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/21e175b862c624d7a2d07802141187edf2d2e489 ))
* support script evaluate arguments
([#40 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/40 ))
([c663f4dhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/c663f4d7f9c0b868e8b4750f6441525939bfe920 ))
* use Performance Trace Formatter in trace output
([#36 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/36 ))
([0cb6147https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0cb6147b870e17bc3a624e9c6396d963a3e16b44 ))
* validate uids
([#37 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/37 ))
([014a8bchttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/014a8bc52ecc58080cedeb8023d44f4a55055a05 ))
### Bug Fixes
* change profile folder name to browser-profile
([#39 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/39 ))
([36115d7https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/36115d757abbae0502ffee814f55368d2ca59b9e ))
* refresh context based on the browser instance
([#44 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/44 ))
([93f4579https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/93f4579dd9aca3beef2bd9f2930ddfcc4069c0e3 ))
* update puppeteer to fix a11y snapshot issues
([#43 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/43 ))
([b58f787https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/b58f787234a34d5fcb01b336f5fb14e1c55ecdd5 ))
---
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-17 13:19:26 +00:00
642d146269
ci: remove provenance while private ( #49 )
2025-09-17 15:09:00 +02:00
785927a38f
chore: Revert "chore(main): release chrome-devtools-mcp 0.2.0" ( #48 )
...
Reverts ChromeDevTools/chrome-devtools-mcp#47
still fails
2025-09-17 15:08:36 +02:00
13ab15fe01
chore(main): release chrome-devtools-mcp 0.2.0 ( #47 )
...
🤖 I have created a release *beep* *boop*
---
##
[0.2.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.1.0...chrome-devtools-mcp-v0.2.0 )
(2025-09-17)
### Features
* add performance_analyze_insight tool.
([#42 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/42 ))
([21e175bhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/21e175b862c624d7a2d07802141187edf2d2e489 ))
* support script evaluate arguments
([#40 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/40 ))
([c663f4dhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/c663f4d7f9c0b868e8b4750f6441525939bfe920 ))
* use Performance Trace Formatter in trace output
([#36 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/36 ))
([0cb6147https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0cb6147b870e17bc3a624e9c6396d963a3e16b44 ))
* validate uids
([#37 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/37 ))
([014a8bchttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/014a8bc52ecc58080cedeb8023d44f4a55055a05 ))
### Bug Fixes
* change profile folder name to browser-profile
([#39 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/39 ))
([36115d7https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/36115d757abbae0502ffee814f55368d2ca59b9e ))
* refresh context based on the browser instance
([#44 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/44 ))
([93f4579https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/93f4579dd9aca3beef2bd9f2930ddfcc4069c0e3 ))
* update puppeteer to fix a11y snapshot issues
([#43 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/43 ))
([b58f787https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/b58f787234a34d5fcb01b336f5fb14e1c55ecdd5 ))
---
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-17 13:04:44 +00:00
7db9d82e5c
ci: fix npm version in publish ( #46 )
...
Following
https://docs.npmjs.com/trusted-publishers#supported-cicd-providers more
closely
2025-09-17 12:57:08 +00:00
181131736d
chore: Revert "chore(main): release chrome-devtools-mcp 0.2.0" ( #45 )
...
Reverts ChromeDevTools/chrome-devtools-mcp#38
Publishing failed, will re-land
2025-09-17 14:50:32 +02:00
4469bf99bd
chore(main): release chrome-devtools-mcp 0.2.0 ( #38 )
...
🤖 I have created a release *beep* *boop*
---
##
[0.2.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.1.0...chrome-devtools-mcp-v0.2.0 )
(2025-09-17)
### Features
* add performance_analyze_insight tool.
([#42 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/42 ))
([21e175bhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/21e175b862c624d7a2d07802141187edf2d2e489 ))
* support script evaluate arguments
([#40 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/40 ))
([c663f4dhttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/c663f4d7f9c0b868e8b4750f6441525939bfe920 ))
* use Performance Trace Formatter in trace output
([#36 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/36 ))
([0cb6147https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/0cb6147b870e17bc3a624e9c6396d963a3e16b44 ))
* validate uids
([#37 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/37 ))
([014a8bchttps://github.com/ChromeDevTools/chrome-devtools-mcp/commit/014a8bc52ecc58080cedeb8023d44f4a55055a05 ))
### Bug Fixes
* change profile folder name to browser-profile
([#39 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/39 ))
([36115d7https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/36115d757abbae0502ffee814f55368d2ca59b9e ))
* refresh context based on the browser instance
([#44 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/44 ))
([93f4579https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/93f4579dd9aca3beef2bd9f2930ddfcc4069c0e3 ))
* update puppeteer to fix a11y snapshot issues
([#43 ](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/43 ))
([b58f787https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/b58f787234a34d5fcb01b336f5fb14e1c55ecdd5 ))
---
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-17 12:40:30 +00:00
93f4579dd9
fix: refresh context based on the browser instance ( #44 )
2025-09-17 14:38:13 +02:00
21e175b862
feat: add performance_analyze_insight tool. ( #42 )
2025-09-17 12:25:40 +00:00
browser-automation-bot