chrome-devtools-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_DEBUGGING_PORT | No | The port for Chrome DevTools Protocol debugging | 9222 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tabsA | 列出当前浏览器所有可调试的 Tab（仅显示 page 类型） |
| query_selectorA | 在 DOM 中查找匹配选择器的所有元素，返回元素基本信息（tagName/id/classList） |
| get_dom_treeA | 获取 DOM 子树结构，可按选择器定位根节点，depth 控制层级深度（最大 10） |
| get_ancestorsA | 获取元素的完整祖先链，每个祖先节点包含指定样式属性值。专为 sticky/overflow/z-index 层叠问题根因定位设计。 |
| get_computed_stylesA | 获取元素所有计算样式（浏览器最终计算值），返回完整的 property: value 键值对 |
| get_matched_stylesA | 获取元素匹配的 CSS 规则列表，包含选择器、来源文件、行号和所有属性 |
| get_box_modelC | 获取元素盒模型尺寸（width/height/margin/padding/border/content） |
| get_layout_metricsA | 获取页面视口尺寸和内容尺寸（viewportWidth/viewportHeight/contentWidth/contentHeight） |
| evaluate_jsA | 在页面上下文中执行 JavaScript 表达式，返回执行结果。禁止访问 cookie/localStorage/fetch 等敏感 API。 |
| get_console_logsC | 获取页面控制台日志（MCP 连接后产生的日志） |
| get_network_requestsA | 获取页面网络请求记录（MCP 连接后发生的请求），可按 URL 关键词过滤 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct aspect of browser inspection: layout, tabs, DOM query, DOM tree, ancestors, styles, box model, JS execution, console, and network. Even the two style-related tools (computed vs. matched) are clearly differentiated.
All tool names follow a consistent verb_noun pattern (get_, list_, query_, evaluate_), making the API predictable and easy to reason about. No mixed conventions or vague verbs.
11 tools is well-scoped for a browser debugging server. Each tool covers a distinct capability without unnecessary overlap, and the count feels appropriate for the intended breadth.
The surface covers DOM, CSS, layout, JS evaluation, console, and network inspection, which are core for debugging. Missing interaction features (e.g., click, navigate, modify styles) suggest a read-only inspector, but that's consistent with the tool descriptions; minor gaps like screenshots or performance tracking could be added.