跟讀練習: How to set up Chrome DevTools for agents - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
80 句
如果句子過短或過長,請點選 Edit 進行調整。
1
Hi, I'm Matthias from the Chrome Developer Relations team.
2
A little while ago, we introduced the Chrome DevTools MCP Server.
3
This episode is a straightforward guide on how to set up the Chrome DevTools MCP Server in Gemini CLI,
4
Cloud and Code Editors like Antigravity and VS Code.
5
We'll look at environment requirements, installing the MCP Server using command line options to tailor it to your needs
6
and how to connect it to a running Chrome instance.
7
For written install instructions for over 15 agentic coding tools, see our README at google slash devtoolsmcp.
8
If you zoned out after I said MCP for the first time and need to catch up, a real brief summary.
9
MCP is a protocol enabling coding agents to talk to external tools like Chrome DevTools.
10
To learn more, watch our intro video about the Chrome DevTools MCP Server first
11
and come back to this video here to start using it.
12
The Chrome DevTools MCP Server is a Node .js application requiring version 20 .19 or newer.
13
To understand which version you have installed on your system in a terminal type node dash dash version.
14
If in your terminal you get output like v25 .1 .0, you're all set.
15
If you get output like command not found, go to the Node .js website and follow the instructions to download and install
16
Node .js for your system.
17
If your version output prints a version number below 20 .19, you need to update
18
Node .js before you can continue.
19
Use the same method you used to install
20
Node .js originally to update it.
21
For example, if you installed
22
Node .js through the Node version manager,
23
nvm, run the command nvm use –lts to download and use the most recent long -term stable version.
24
After verifying your Node .js installation, a few words on scoping.
25
This tutorial will guide you through installing the Chrome DevTools MCP server to a specific
26
Node .js project, instead of installing it for your user.
27
This is recommended, as every MCP server comes with a token cost
28
and you only want to have MCP servers enabled in chat sessions where you actually use them.
29
Additionally, this allows for a project -specific configuration of the MCP server. And lastly,
30
this will persist which MCP servers are used in a project to your repository
31
so your peers can use the same MCP service with the same configuration you do.
32
So when following this tutorial, make sure your current working directory has a package JSON or alternatively create a new one by running npm init.
33
Finally, before you get actually started with the Chrome DevTools MCP server, your coding agent might have built -in browser tools.
34
To not confuse your model with overlapping tools, make sure to disable them before proceeding.
35
Now that your environment meets all requirements, we are going to look into installing the Chrome DevTools MCP server.
36
Let's start with Gemini CLI.
37
Gemini CLI provides a handy install command that you see here.
38
This command invokes Gemini CLI, running the MCP command with the add sub command and the name of the server and its run command as arguments.
39
Run this command to install the Chrome DevTools MCP server to use in your current project with Gemini CLI.
40
For Cloud Code, there is a similar command, just as you see here.
41
Now, the interesting thing about those project scoped commands is that they generate a standardized configuration file.
42
For Gemini CLI, it's at dot gemini slash settings json
43
and for cloud code it's at dot mcp dot json in your project root
44
you can create the same configuration file for vius code for vius code
45
it needs to be at dot vius code slash mcp dot
46
json in your project root directory the same works for other
47
vius code based editors like cursor using the dot cursor slash mcp json file.
48
So when setting up mcp servers, make sure to commit configuration to your repository for any editor that's widely used in your team.
49
When your colleagues do their next git poll, their coding agent will then auto -discover and install mcp servers from the configuration files.
50
Now that we have set up our environment and the server, we can look into tailoring it to our needs.
51
The Chrome DevTools MCP server offers a wide range of tools
52
for various debugging tasks to enable your coding agent to autonomously investigate and fix bugs and validate its own output.
53
There are tools to fill forms, emulate aspects like screen size, location, CPU and network speed,
54
and to measure performance or run lighthouse audits.
55
However, you might not need all the available tools in your project.
56
For example, while debugging a form, you might not care about testing it across various devices, so you don't need the emulation tools.
57
And if you already extensively tested performance, you might not need the performance tools.
58
So you might want to disable them to not pay token costs for their definition.
59
To enable those and other use cases, you can tailor the DevTools MCP server to your needs using configuration flags.
60
The Chrome DevTools MCP server offers over 20 flags to tune various aspects of the server.
61
To get an overview of all available tools and configuration options, see our tool reference and read me at google slash devtools mcp.
62
There are also configuration flags for the previously mentioned example.
63
You can explicitly enable or disable certain tool categories.
64
Let's look into how to apply them.
65
This is our current configuration file.
66
To apply configuration options, create a new entry in the args array.
67
For example, to disable the emulation tools, add this line, dash dash category emulation equals false.
68
Or to use the slim mode with the least token consumption and only navigation and a screenshot tool, use dash dash slip.
69
You can also use the dash dash auto -connect option to let your agent use an already running
70
Chrome instance like this.
71
To use auto -connect, you also need to enable remote debugging in your Chrome instance by going to Chrome Inspect Remote Debugging.
72
Once you have configured the Chrome DevTools MCP server to your liking, or if you're happy with the defaults, you're ready for your first steps.
73
For example, you can now ask your coding agent to run a lighthouse audit for any site.
74
But you can also ask it to debug more complex flows like go to localhost admin
75
and log in with user admin and pass admin.
76
Create a new page titled
77
Hello from DevTools MCP and save it and then live observe your agent testing the full flow.
78
Start with a simple prompt to check if your setup works.
79
If you're running into issues, check our troubleshooting hints at google .devtools .mcp or let us know in the comments below.
80
So, thanks for watching and see you next time.
FOR YOU
推薦影片
本課的詞彙與口語要點
這節口語課以影片“How to set up Chrome DevTools for agents”為素材。 影片中反覆出現的詞有:mcp, server, Chrome, devtools, tool。 這段影片共有 80 個句子、1139 個單詞可供跟讀。 講話部分時長為 7:57。 說話人語速平穩,每分鐘約 143 個詞,很適合跟讀。 只有 69% 的單詞屬於英語最常用的 3,000 詞,詞彙難度較高。
影片中的重點詞彙
影片中 15 個值得學習的單詞,附發音和釋義:
| 單詞 | 發音 | 釋義 |
|---|---|---|
| server 名詞 | /ˈsɝvɚ/ | 伺服器 /伺服器, 伺服器 |
| configuration 名詞 | /kənˌfɪɡ.əˈɹeɪ̯.ʃən/ | 編排 /編排, 配置 |
| install 動詞 | /ɪnˈstɔl/ | 安裝 /安裝 |
| node 名詞 | /noʊd/ | 結節 /結節 |
| dash 名詞 | /ˈdæʃ/ | 破折號 /破折號 |
| output 名詞 | /ˈaʊtpʊt/ | 輸出 /輸出 |
| cloud 名詞 | /ˈklaʊ̯d/ | йүн, 雲 /雲 |
| connect 動詞 | /kəˈnɛkt/ | 連線 /連線 |
| token 名詞 | /ˈtoʊkən/ | 代幣 /代幣, 籌碼 /籌碼 |
| tailor 名詞 | /ˈteɪlɚ/ | 裁縫 /裁縫, 裁縫師傅 /裁縫師傅 |
| aspect 名詞 | /ˈæspɛkt/ | 方面 |
| remote 形容詞 | /ɹəˈməʊt̞/ | 遠 /遠, 遙遠 /遙遠 |
| terminal 名詞 | /ˈtɚmɪnəl/ | 航站, 航廈 /航廈 |
| requirement 名詞 | /ɹɪˈkwaɪɹmənt/ | 要求, 需求 |
| scope 名詞 | /skəʊp/ | 範圍 /範圍 |
影片中的語法
說話人最常用的結構,並附上影片中的原話:
| 結構 | 影片中的用法 |
|---|---|
| 現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事 | have installed · have set · have configured |
| 被動語態 be + 過去分詞 — 強調發生了什麼,而不是誰做的 | is recommended · are used |
需要注意的發音
說話人用了 7 次縮略和弱讀形式,例如 you're, don't, I'm。請按聽到的簡短形式來說。
- “sh” 和 “zh” 音: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, dash /ˈdæʃ/, instruction /ɪnˈstɹʌkʃən/, consumption /kənˈsʌmp.ʃən/, installation /ˌɪn.stəˈleɪ.ʃən/
- 長單詞——注意重音位置: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, directory /dɪˈɹɛktəɹi/, investigate /ɪnˈvɛs.tə.ɡeɪt/, installation /ˌɪn.stəˈleɪ.ʃən/, navigation /nævɪˈɡeɪʃən/
中文母語者容易讀錯的音:
- /v/ — 不要讀成 /w/,上齒輕觸下唇: server /ˈsɝvɚ/, discover /dɪˈskʌvə/, investigate /ɪnˈvɛs.tə.ɡeɪt/, overview /ˈoʊ.vɚˌvjuː/, observe /əbˈzɜːv/
- 詞尾子音 — 要讀清楚,後面不要加母音: node /noʊd/, dash /ˈdæʃ/, output /ˈaʊtpʊt/, cloud /ˈklaʊ̯d/, connect /kəˈnɛkt/
- /r/ 和 /l/ 的區別: tutorial /ˌtjuːˈtɔːɹɪəl/, protocol /ˈpɹoʊtəˌkɑl/
如何用這段影片練習
- 先完整聽一遍影片,不要開口,記下不認識的單詞。
- 用正常速度逐句跟讀,每句重複到你的節奏與說話人一致為止。
- 錄下自己的聲音並與原聲對比,特別注意 server, configuration, install 這類單詞。
什麼是跟讀法?
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧,最初開發用於專業口譯員的培訓,並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大:您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同,跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性,語調,節奏,連讀,聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。












