browser-use-native-windows
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BROWSER_USE_NATIVE_WINDOWS_SSE_AUTH | No | SSE bearer token. | change.me |
| BROWSER_USE_NATIVE_WINDOWS_SSE_HOST | No | SSE bind host. | 127.0.0.1 |
| BROWSER_USE_NATIVE_WINDOWS_SSE_PORT | No | SSE bind port. | 7331 |
| BROWSER_USE_NATIVE_WINDOWS_NO_SANDBOX | No | Add browser no-sandbox launch args. | false |
| BROWSER_USE_NATIVE_WINDOWS_BLOCKED_URL_RULES | No | Semicolon-separated wildcard URL/path block rules. | |
| BROWSER_USE_NATIVE_WINDOWS_FORCE_STOP_HOTKEY | No | Override the global force-stop hotkey. | Control+F12 |
| BROWSER_USE_NATIVE_WINDOWS_BROWSER_EXTRA_ARGS | No | Extra launch args separated by spaces. | |
| BROWSER_USE_NATIVE_WINDOWS_BROWSER_USER_DATA_DIR | No | Override package-local browser profile directory. | |
| BROWSER_USE_NATIVE_WINDOWS_BROWSER_EXECUTABLE_PATH | No | Override browser executable auto-detection. | |
| BROWSER_USE_NATIVE_WINDOWS_DISABLE_FORCE_STOP_HOTKEY | No | Disable the force-stop watchdog when true. | false |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_observeC | Launch or adopt a Windows browser, optionally handle a target URL through native UI, and return a browser-window or browser-owned file-dialog observation. |
| browser_actB | Run one native mouse or keyboard action against a matching fresh browser_observe token. |
| browser_statusB | Return MCP transport, native input driver, browser process, HWND, monitor, DPI, focus, and observation state. |
| browser_stopA | Release held native input state and optionally close the tracked browser only when the user task asks for it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| browser_use_native_windows | Use browser-use-native-windows with native screenshots, accessibility, mouse, and keyboard. |
| browser_use_native_windows_recovery | Recover from stale observations, focus changes, bounds changes, and missing native input driver. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| runtime-status | Current browser-use-native-windows runtime state. |
| instructions | Native Windows browser-use instructions. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: browser_observe for launching/adopting and getting observation, browser_act for performing actions, browser_status for checking state, and browser_stop for cleanup. No overlap in purpose.
All tool names follow a consistent 'browser_' prefix followed by a single verb (observe, act, status, stop), all lowercase, with no mixing of conventions.
Four tools is exactly right for this domain: observe, act, status, and stop cover the essential lifecycle without unnecessary extras. Not too few, not too many.
The tool set covers the full lifecycle of native browser interaction: initialization (browser_observe), action (browser_act), monitoring (browser_status), and termination (browser_stop). No obvious gaps.