シャドーイング練習: 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発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える
FOR YOU

おすすめ動画

このレッスンの語彙とスピーキングのポイント

このスピーキングレッスンは、動画「How to set up Chrome DevTools for agents」を教材にしています。 繰り返し出てくる語は次のとおりです:mcp, server, Chrome, devtools, tool。 この動画には、シャドーイング用の文が80文、単語が1139語あります。 音声の長さは7:57です。 話す速さは1分あたり約143語で安定しており、シャドーイングしやすいペースです。 英語の頻出3,000語に含まれる単語は69%だけなので、語彙は難しめです。

この動画の重要語彙

動画に出てくる覚えておきたい単語15語を、発音と意味つきで紹介します。

単語発音意味
server 名詞/ˈsɝvɚ/サーバー
configuration 名詞/kənˌfɪɡ.əˈɹeɪ̯.ʃən/構成, 配置
install 動詞/ɪnˈstɔl/導入する, インストールする
node 名詞/noʊd/結節
dash 名詞/ˈdæʃ/長点
output 名詞/ˈaʊtpʊt/出力
disable 動詞/dɪsˈeɪbəl/無力化する
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/要求

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型動画での表現
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係しているhave installed · have set · have configured
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てるis recommended · are used

注意したい発音

話し手はyou're, don't, I'mなど、短縮形や弱形を7回使っています。聞こえたとおりの短い形で発音しましょう。

  • 「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/

日本語話者が苦手な音:

  • /r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: tutorial /ˌtjuːˈtɔːɹɪəl/, protocol /ˈpɹoʊtəˌkɑl/
  • /v/ — /b/ にならないように、上の歯を下唇に当てる: server /ˈsɝvɚ/, discover /dɪˈskʌvə/, investigate /ɪnˈvɛs.tə.ɡeɪt/, overview /ˈoʊ.vɚˌvjuː/, observe /əbˈzɜːv/
  • /f/ — 「フ」ではなく、上の歯と下唇で出す: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, default /dɪˈfɔlt/, verify /ˈvɛɹɪfaɪ/, straightforward /ˌstɹeɪtˈfɔː(ɹ)wə(ɹ)d/, confuse /kənˈfjuːz/

この動画での練習方法

  1. まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
  2. 通常の速度で一文ずつシャドーイングし、話し手のリズムに合うまで繰り返します。
  3. 自分の声を録音して元の音声と比べます。server, configuration, installなどの単語に特に注意しましょう。

シャドーイングとは?英語上達に効果的な理由

シャドーイング(Shadowing)は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的:ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影(shadow)」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →