opencode-browser-control
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 |
|---|---|
| browserC | 浏览器控制主工具。通过 action 参数选择操作。首次使用自动启动浏览器。 |
| browser_snapshotA | 获取页面 ARIA 可访问性快照，返回带编号引用（e1, e2...）的交互元素列表。使用 browser_click(ref) 点击这些元素。 |
| browser_clickA | 通过 ARIA 快照引用（如 e42）点击页面元素。需先调用 browser_snapshot 获取引用。 |
| browser_typeA | 通过 ARIA 快照引用在输入框中输入文本。需先调用 browser_snapshot 获取引用。 |
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 4 tools
Each tool has a clearly distinct purpose: browser for general control, snapshot for getting ARIA references, click for clicking elements, and type for typing text. No overlap in functionality.
All tools use the 'browser_' prefix, providing a consistent pattern. The main tool is simply 'browser', which deviates slightly from the verb_noun pattern but is still clear and predictable.
With 4 tools covering core browser control (navigation, snapshot, click, type), the count is well-scoped and appropriate for the domain.
The tool set covers essential browser interactions, but lacks explicit support for scrolling, keyboard actions, or file handling. Minor gaps that can be worked around.