browser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| navigateC | 访问指定的URL网页 |
| get_page_sourceA | 获取当前页面的完整HTML源码 |
| get_element_stylesA | 获取指定元素的所有CSS样式（包括计算后的样式） |
| get_all_stylesheetsB | 获取页面所有CSS样式表的内容 |
| extract_css_classesA | 提取页面中所有CSS类的定义和使用情况 |
| get_element_by_selectorC | 通过CSS选择器获取元素的HTML和样式信息 |
| download_assetsA | 获取页面所有静态资源的URL列表（CSS、字体、图片等） |
| analyze_layoutB | 分析页面布局结构（Flexbox、Grid等） |
| get_fontsA | 获取页面使用的所有字体信息 |
| screenshotC | 对当前页面或指定元素截图 |
| execute_scriptB | 在页面中执行自定义JavaScript代码 |
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
Most tools have distinct purposes, but there is minor overlap between get_element_by_selector and get_element_styles (both return style info) and between download_assets and get_fonts (both list fonts). Overall, the boundaries are clear enough for an agent.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_layout, download_assets, get_element_styles). Even single-word tools like 'navigate' and 'screenshot' fit the imperative style. No mixing of conventions.
With 11 tools, the server is well-scoped for browser inspection and debugging tasks. Each tool covers a clear aspect (navigation, HTML, CSS, layout, assets, scripts, screenshots) without redundancy or bloat.
The tools cover static analysis well but lack interactive capabilities such as clicking, form filling, cookie management, or network request interception. This may leave agents unable to perform dynamic browser automation tasks.