mirrors / chromedevtools--chrome-devtools-mcp

提交

871 提交 46 分支 57 Git 标签
protp-diff-tools
提交图

871 次代码提交

此分支
此分支
所有分支
作者 SHA1 备注 提交日期
Coquinate 139cfd135c feat(screenshot): add JPEG quality parameter support (#184) 
## Summary

This PR adds support for the `quality` parameter when taking JPEG
screenshots, allowing users to control compression levels and
significantly reduce file sizes.

## Problem

Currently, the Chrome DevTools MCP doesn't expose the `quality`
parameter that Puppeteer natively supports. This leads to:
- Large screenshot file sizes (especially problematic for AI assistants
with image size limits)
- No control over JPEG compression 
- Inability to optimize screenshots for different use cases

## Solution

Added the `quality` parameter (0-100) to the screenshot tool schema and
passed it through to Puppeteer's screenshot method.

## Changes

- ✅ Added `quality` parameter to screenshot schema with proper
validation (0-100 range)
- ✅ Pass quality parameter to Puppeteer's `screenshot()` method
- ✅ Added `optimizeForSpeed` flag for improved encoding performance
- ✅ Updated documentation via `npm run docs`

## Testing

Tested locally with various quality settings:
- **PNG (baseline):** 128 KB
- **JPEG quality 100:** 245 KB
- **JPEG quality 50:** 84 KB (35% reduction)
- **JPEG quality 30:** 66 KB (49% reduction)

## Impact

This change is **backward compatible** - the quality parameter is
optional and doesn't affect existing usage. It particularly helps with:
- AI assistants that have image size limits (e.g., 8000px max dimension
errors)
- Reducing bandwidth when capturing many screenshots
- Optimizing storage for screenshot-heavy workflows

## Example Usage

```javascript
// New capability - control JPEG quality
await take_screenshot({
  format: 'jpeg',
  quality: 50,  // New parameter!
  fullPage: false
})
```

## Checklist

- [x] Code follows conventional commits
- [x] Documentation updated with `npm run docs`
- [x] Tested locally
- [x] Backward compatible
- [ ] CLA signed (will complete if needed)

Fixes #[issue-number] (if applicable)

Co-authored-by: aberemia24 <aberemia@gmail.com>
 2025-09-29 14:00:36 +00:00
Alex Rudenko d9f77f8509 fix: do not error if the dialog was already handled (#208) 
users report that the MCP client gets stuck if the dialog was closed
manually as the MCP state never updates.
 2025-09-29 13:53:25 +00:00
Alex Rudenko 13613b4a33 fix: support node20 (#52) 
Initially, we started with the support of Node22+ but since Node20 is an
LTS that is still in the maintenance mode it makes sense to support it.
 2025-09-29 13:43:35 +00:00
Alex Rudenko 7765bb381a fix: update tool reference in an error (#205) 
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/170 
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/169
 2025-09-29 13:11:17 +00:00
dependabot[bot] 1f4007ed90 chore(deps): bump @modelcontextprotocol/sdk from 1.18.1 to 1.18.2 in the dependencies group (#187) 
Bumps the dependencies group with 1 update:
[@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk).

Updates `@modelcontextprotocol/sdk` from 1.18.1 to 1.18.2
<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.2</h2>
<h2>What's Changed</h2>
<ul>
<li>Updates the sampling code example in the README by <a
href="https://github.com/viniciuscsouza"><code>@​viniciuscsouza</code></a>
in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/958">modelcontextprotocol/typescript-sdk#958</a></li>
<li>Use redirect Uri passed in in <code>demoInMemoryOAuthProvider</code>
by <a
href="https://github.com/TylerLeonhardt"><code>@​TylerLeonhardt</code></a>
in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/931">modelcontextprotocol/typescript-sdk#931</a></li>
<li>fix(auth-router): correct Protected Resource Metadata for pathful RS
and add explicit resourceServerUrl (RFC 9728) by <a
href="https://github.com/blustAI"><code>@​blustAI</code></a> in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/858">modelcontextprotocol/typescript-sdk#858</a></li>
<li>chore: update version to 1.18.2 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/970">modelcontextprotocol/typescript-sdk#970</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a
href="https://github.com/viniciuscsouza"><code>@​viniciuscsouza</code></a>
made their first contribution in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/958">modelcontextprotocol/typescript-sdk#958</a></li>
<li><a
href="https://github.com/TylerLeonhardt"><code>@​TylerLeonhardt</code></a>
made their first contribution in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/931">modelcontextprotocol/typescript-sdk#931</a></li>
<li><a href="https://github.com/blustAI"><code>@​blustAI</code></a> made
their first contribution in <a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/858">modelcontextprotocol/typescript-sdk#858</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/modelcontextprotocol/typescript-sdk/compare/1.18.1...1.18.2">https://github.com/modelcontextprotocol/typescript-sdk/compare/1.18.1...1.18.2</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/modelcontextprotocol/typescript-sdk/commit/058b87c163996b31d5cda744085ecf3c13c5c56a"><code>058b87c</code></a>
chore: update version to 1.18.2 for weekly release (<a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/970">#970</a>)</li>
<li><a
href="https://github.com/modelcontextprotocol/typescript-sdk/commit/1d475bb3f75674a46d81dba881ea743a763cbc12"><code>1d475bb</code></a>
fix(auth-router): correct Protected Resource Metadata for pathful RS and
add ...</li>
<li><a
href="https://github.com/modelcontextprotocol/typescript-sdk/commit/9841a6cf2959d0f361ac5eee6e1a2e0f3515b943"><code>9841a6c</code></a>
Use redirect Uri passed in in <code>demoInMemoryOAuthProvider</code> (<a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/931">#931</a>)</li>
<li><a
href="https://github.com/modelcontextprotocol/typescript-sdk/commit/c342dacb5ed55a0366fd2512bb642d1ceaa2ed87"><code>c342dac</code></a>
Updates the sampling code example in the README (<a
href="https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/958">#958</a>)</li>
<li>See full diff in <a
href="https://github.com/modelcontextprotocol/typescript-sdk/compare/1.18.1...1.18.2">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@modelcontextprotocol/sdk&package-manager=npm_and_yarn&previous-version=1.18.1&new-version=1.18.2)](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-29 15:08:56 +02:00
browser-automation-bot 420251383e chore(main): release chrome-devtools-mcp 0.4.0 (#157)
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.4.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v0.3.0...chrome-devtools-mcp-v0.4.0)
(2025-09-26)


### Features

* add network request filtering by resource type
([#162](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/162))
([59d81a3](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/59d81a33258a199a3f993c9e02a415f62ef05ce4))


### Bug Fixes

* add core web vitals to performance_start_trace description
([#168](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/168))
([6cfc977](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/6cfc9774f4ec7944c70842999506b2bc2018a667))
* add data format information to trace summary
([#166](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/166))
([869dd42](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/869dd4273e42309c1bb57d44e0e5a6a9506ffad7))
* expose --debug-file argument
([#164](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/164))
([22ec7ee](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/22ec7ee45cc04892000cf6dc32f3fe58d33855c1))
* typo in the disclaimers
([#156](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/156))
([90f686e](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/90f686e5df3d880c35ec566c837ee5a98824be28))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
chrome-devtools-mcp-v0.4.0 		2025-09-26 16:03:54 +02:00
Julien eaecc2448c docs: improved instructions for Gemini CLI MCP server (#161) 
Added CLI installation instructions for Chrome DevTools MCP server using
Gemini CLI.

---------

Co-authored-by: Alex Rudenko <alexrudenko@chromium.org>
 2025-09-26 13:24:18 +00:00
Oz Tamir 59d81a3325 feat: add network request filtering by resource type (#162) 
### Summary
This PR build upon #145 to also adds filtering by resource type to
`list_network_requests` (Also see: #137 and #107).

### Motivation
Agents often need specific request types (e.g., scripts, stylesheets,
images). Filtering reduces noise and improves performance.

### Changes
- **New parameter**: `resourceType` (array) to filter by resource types
- **Supported types**: all resource types supported by Puppeteer
- **Backward compatible**: when omitted, returns all requests

Filtering runs before pagination, so pagination applies to the filtered
results.
 2025-09-26 13:17:58 +00:00
Jack Franklin 6cfc9774f4 fix: add core web vitals to performance_start_trace description (#168) 
Fixes #124 and #159. People have reported that when asked for CWV
metrics, the AI will use `evaluate_script` to inject some code into the
page to gather them. But, we want to encourage it to record a trace
instead and use those values.

After some testing locally, adding CWV explicitly to the description
makes it much more reliable that the AI will reach for trace recording
when asked about CWVs.
 2025-09-26 13:14:27 +00:00
Jack Franklin 869dd4273e fix: add data format information to trace summary (#166) 
This CL adds the descriptions of the call frame format and the network
request format to the summary so that as the AI sees these responses it
can fully parse them.
 2025-09-26 14:12:00 +01:00
Alex Rudenko 22ec7ee45c fix: expose --debug-file argument (#164) 2025-09-26 09:00:04 +00:00
Jack Franklin 2dbdd2de4f chore: roll latest chrome-devtools-frontend (#163) 
This includes a better fix for the circular dependency problem and makes
the changes in the MCP server based on the upstream DevTools
implementation changes.
 2025-09-26 09:44:03 +01:00
Nikolay Vitkov 6d9cd17714 chore: unblock uses with Deno and Bun (#151) 
I wanna test more NodeJS versions to see that this does not cause other
issues.

Deno test command: 
```sh
npx @modelcontextprotocol/inspector deno --allow-env --allow-read ./build/src/index.js 
```

Bun test command:
```sh
npx @modelcontextprotocol/inspector bun ./build/src/index.js 
```
 2025-09-26 08:31:41 +02:00
Alex Rudenko 90f686e5df fix: typo in the disclaimers (#156) 2025-09-25 21:32:11 +02:00
browser-automation-bot 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))
([4c909bb](https://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))
([44cfc8f](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/44cfc8f945edf9370efe26247f322a59a4a4a7be))
* clarify the node version message
([#135](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/135))
([0cc907a](https://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))
([03b59f0](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/03b59f0bca024173ad45d7a617994e919d9cbbad))
* **performance:** ImageDelivery insight errors
([#144](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/144))
([d64ba0d](https://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))
([b2e1e39](https://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).
chrome-devtools-mcp-v0.3.0 		2025-09-25 18:51:31 +02:00
Alex Rudenko 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
Jack Franklin 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
Nikolay Vitkov 15277541d8 chore: add additional EsLint rule (#147) 2025-09-25 17:20:01 +02:00
Oz Tamir 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
Jack Franklin 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
Alex Rudenko 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
Jan-Niklas W. 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
Alex Rudenko 5cfa7150fc chore: latest gemini extension (#142) 2025-09-25 09:41:25 +00:00
Alex Rudenko 0cc907a9ad fix: clarify the node version message (#135) 2025-09-25 08:39:19 +02:00
Alex Rudenko 3597a3b4cf chore(deps): bump puppeteer (#128) 2025-09-24 21:35:08 +02:00
Alex Rudenko e5b6600022 docs: fix readme (#122) 
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/119
 2025-09-24 14:48:15 +00:00
Alex Rudenko 2b315b78fc chore: add npx command (#120) 2025-09-24 16:32:18 +02:00
Alex Rudenko b53f114738 chore: update gemini-extension.json (#118) 2025-09-24 14:13:23 +00:00
browser-automation-bot 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))
([adfcecf](https://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).
chrome-devtools-mcp-v0.2.7 		2025-09-24 14:55:21 +02:00
Alex Rudenko 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
Alex Rudenko c9fdd2ce12 chore: add gemini extension json (#114) 2025-09-24 14:38:37 +02:00
Alex Rudenko f2fe7f0e5e test: add node23 to the matrix (#100) 2025-09-24 09:28:57 +00:00
browser-automation-bot 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))
([cae1cf1](https://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).
chrome-devtools-mcp-v0.2.6 		2025-09-24 08:30:56 +00:00
Alex Rudenko 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
browser-automation-bot 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))
([bd0351f](https://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).
chrome-devtools-mcp-v0.2.5 		2025-09-24 10:02:12 +02:00
Alex Rudenko bd0351fd36 fix: add mcpName to package.json (#103) 2025-09-24 07:59:37 +00:00
browser-automation-bot 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))
([0ca2434](https://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).
chrome-devtools-mcp-v0.2.4 		2025-09-24 09:52:42 +02:00
Alex Rudenko 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
Alex Rudenko 2ee30bf37b chore: latest mcp registry schema (#101) 2025-09-24 07:21:36 +00:00
browser-automation-bot 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))
([1a4ba4d](https://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))
([4e7001a](https://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).
chrome-devtools-mcp-v0.2.3 		2025-09-24 07:08:12 +00:00
Kingsword cb17ae80e6 docs: add Codex MCP configuration guide (#95) 
Co-authored-by: Sebastian Benz <sbenz@google.com>
 2025-09-24 08:48:06 +02:00
Alex Rudenko 8d0cb79b50 chore: update mcp publisher (#98) 2025-09-24 06:20:17 +00:00
Sebastian Benz 82bd72aef7 chore: fix label for feature request issues (#97) 2025-09-24 08:00:04 +02:00
Sebastian Benz 1ed7e45fef docs: explain when the browser starts (#89) 2025-09-23 20:13:03 +00:00
Alex Rudenko 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
Nikolay Vitkov 4e7001ac37 fix: clean up pending promises on action errors (#84) 2025-09-23 18:33:50 +00:00
browser-automation-bot 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))
([d6bab91](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/d6bab912df55dc2e96a8d7893d1906f1fc608d0a))
* remove unnecessary waiting for navigation
([#83](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/83))
([924c042](https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/924c042492222a555074063841ce765342e3b5b9))
* rework performance parsing & error handling
([#75](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/75))
([e8fb30c](https://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).
chrome-devtools-mcp-v0.2.2 		2025-09-23 18:26:00 +00:00
Alex Rudenko 924c042492 fix: remove unnecessary waiting for navigation (#83) 2025-09-23 18:23:53 +00:00
Alex Rudenko 67af3fefe5 chore: publish to MCP registry (#78) 
Includes server.json and the GitHub Actions steps.
 2025-09-23 19:59:48 +02:00
Alex Rudenko 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