mirrors / chromedevtools--chrome-devtools-mcp

文件历史

671 提交 46 分支 57 Git 标签
update-devtools
提交图

11 次代码提交

作者 SHA1 备注 提交日期
Alex Rudenko 1ac574e715 feat: experimental chrome-devtools CLI (#1100) 
This PR enables an alternative CLI interface for Chrome DevTools MCP.
`chrome-devtools` can be used in shell scripts to automate the Chrome
DevTools MCP session running as a daemon process. Currently, a single
session is shared between all `chrome-devtools` calls. All tools
available by default are included into the CLI.

Examples:

```bash
❯ chrome-devtools navigate_page --url https://example.com
Successfully navigated to https://example.com.
## Pages
1: https://example.com/ [selected]

❯ chrome-devtools lighthouse_audit
## Lighthouse Audit Results
Mode: navigation
Device: desktop
URL: https://example.com/
### Category Scores
- Accessibility: 96 (accessibility)
- Best Practices: 96 (best-practices)
- SEO: 80 (seo)
### Audit Summary
Passed: 30
Failed: 4
Total Timing: 4107.22ms
### Reports
- /var/folders/hq/m1wr43z9665g5pghys7gkc2w00r23k/T/chrome-devtools-mcp-l5LRIT/report.json
- /var/folders/hq/m1wr43z9665g5pghys7gkc2w00r23k/T/chrome-devtools-mcp-3o6rcM/report.htm
```

```sh
❯ chrome-devtools lighthouse_audit --format=json | jq
{
  "lighthouseResult": {
    "summary": {
      "mode": "navigation",
      "device": "desktop",
      "url": "https://example.com/",
      "scores": [
        {
          "id": "accessibility",
          "title": "Accessibility",
          "score": 0.96
        },
        {
          "id": "best-practices",
          "title": "Best Practices",
          "score": 0.96
        },
        {
          "id": "seo",
          "title": "SEO",
          "score": 0.8
        }
      ],
      "audits": {
        "failed": 4,
        "passed": 30
      },
      "timing": {
        "total": 3754.87
      }
    },
    "reports": [
      "/var/folders/hq/m1wr43z9665g5pghys7gkc2w00r23k/T/chrome-devtools-mcp-nbLj82/report.json",
      "/var/folders/hq/m1wr43z9665g5pghys7gkc2w00r23k/T/chrome-devtools-mcp-VTp35b/report.html"
    ]
  }
}
```

To test:

```sh
npm ci
npm run clean
npm run bundle
npm pack
npm i chrome-devtools-mcp-0.18.1.tgz -g # to install globally
```

---------

Co-authored-by: Mathias Bynens <mathias@qiwi.be>
 2026-03-11 09:42:12 +01:00
Michael Hablich 57e7d51e8c docs(troubleshooting): add symptom for missing tools due to read-only mode (#1148) 2026-03-09 12:32:47 +00:00
Michael Hablich adac7c537e fix: repair broken markdown and extract snippets in a11y-debugging skill (#1096) 
## Summary
- Fix broken markdown fences in `skills/a11y-debugging/SKILL.md` — a
stray quadruple-backtick on line 72 broke the numbered list
continuation, and a mismatched fence on line 95 disrupted rendering
- Extract verbose JS snippets (orphaned inputs, tap targets, color
contrast, global checks) into `references/a11y-snippets.md`, keeping
SKILL.md scannable and following the same `references/` pattern used by
`debug-optimize-lcp`

## Test plan
- [x] Verify SKILL.md renders correctly in GitHub markdown preview (no
broken fences or orphaned code blocks)
- [x] Verify `references/a11y-snippets.md` renders correctly and all 4
snippets are present
- [x] Confirm the relative links from SKILL.md to
`references/a11y-snippets.md` resolve correctly on GitHub
 2026-03-04 08:05:47 +00:00
Michael Hablich 7273f16ec0 feat: Add skill which helps with onboarding of the mcp server (#1083) 
- **feat: add troubleshooting skill definition and expand documentation
with details on autoConnect timeouts and extension debugging
conflicts.**
- **docs: Simplify troubleshooting skill instructions by removing
explicit tool mentions and updating the troubleshooting guide link.**
- **docs: Update troubleshooting guide to recommend and correct usage of
`--logFile` for capturing debug logs.**
- **docs: Enhance troubleshooting guide with 'Tool not found' error,
`--autoConnect` Chrome 144+ requirement, and `startup_timeout_ms` tip
for Windows.**
- **docs: Clarify that Chrome 144+ must be running for `--autoConnect`
and add a verification step for remote debugging.**
- **feat: Add an initial troubleshooting step to read and interpret MCP
configuration, renumbering subsequent steps.**
- **docs: Add detailed troubleshooting steps for `Could not find
DevToolsActivePort` and other common connection errors.**
- **docs: Add troubleshooting guidance for empty profile creation due to
typos or misconfiguration.**
 2026-03-04 06:55:25 +00:00
Michael Hablich 21634e660c docs: Adapt a11y skill to utilize Lighthouse (#1054) 
- **feat: Add Lighthouse audit as the initial step in the accessibility
debugging workflow and reorder subsequent sections.**
- **feat: Add critical instructions for parsing Lighthouse audit reports
to efficiently extract failing elements.**
 2026-02-27 06:47:06 +00:00
Matthias Rohmer 2cd9b95346 feat: add skill to debug and optimize LCP (#993) 
This is a draft for new skill to debug and optimize LCP scores, going
hand in hand with
https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/831.

Base for this skill is key authoritative learning material from web.dev,
about debugging and optimizing LCP, mainly:

- http://web.dev/articles/lcp
- http://web.dev/articles/optimize-lcp
- https://web.dev/articles/top-cwv

I gave the content of those articles together with the [tool
reference](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md),
the README and the chrome-devtools core skill to both Claude Opus 4.6
and Gemini 3 Pro and their respective skill creator skills. The final
skill in this PR is a merge of multiple runs with both models.

The snippets to run with `evaluate_script` is something only Opus came
up with, but I think it's quite nice, though our own `performance_*`
tools might give the same insight but likely with more overhead (meaning
tokens).
 2026-02-23 15:41:14 +00:00
Alex Rudenko c402b43697 feat: --slim mode for maximum token savings (#958) 
- navigate
- run js
- take screenshot

That's it. Basic functionality for a low (~368) token price.
 2026-02-23 14:42:27 +00:00
Michael Hablich 5cedcaad2c refactor: simplify JavaScript code examples, update code block language, and refine descriptions in a11y debugging skill documentation. (#1009) 2026-02-20 14:04:03 +00:00
Michael Hablich b0c6d042e4 feat: add a new skill for accessibility debugging and auditing with Chrome DevTools MCP. (#1002) 2026-02-20 12:34:00 +00:00
Alex Rudenko 107c46a4db docs: Update README with WSL configuration details (#946) 
Added workarounds for using chrome-devtools-mcp in WSL.

Drive-by: moved known issues from readme to troubleshooting.
Drive-by: updated skill to link to troubleshooting.
Drive-by: rephrased for clarity.
 2026-02-13 08:28:01 +00:00
Alex Rudenko aa0a3679f5 feat: add a skill for using chrome-devtools-mcp (#830) 
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/710
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/709
 2026-01-26 10:04:39 +00:00