跟读练习: 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.

下载应用

流利口语所需的一切

AI 发音评分逐句打分
音标练习掌握每个音
词汇学习建立你的词库
词汇游戏边玩边学
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/

如何用这段视频练习

  1. 先完整听一遍视频,不要开口,记下不认识的单词。
  2. 用正常速度逐句跟读,每句重复到你的节奏与说话人一致为止。
  3. 录下自己的声音并与原声对比,特别注意 server, configuration, install 这类单词。

什么是跟读法?

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧,最初开发用于专业口译员的培训,并由多语言者Alexander Arguelles博士普及。这个方法简单而强大:您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同,跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性,语调,节奏,连读,听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →