Best for
- MCP clients that need browser automation or browser access
- Local or remote environments using Chrome, Edge, or Firefox
- Workflows that connect to a browser through CDP or WebSocket
M
46FMRS · D
The source lists this server as active at version 1.0.0 under the Apache-2.0 license. It is focused on browser-use access; the source does not list specific MCP tools, client compatibility, or authentication mechanisms.
This is the browser MCP server in ByteDance's UI-TARS-desktop repository. It provides browser-use access and can run over stdio, SSE, or Streamable HTTP. It supports Chrome, Edge, and Firefox, with optional CDP or WebSocket connections. Aria snapshots are used by default, with an optional screenshot-based vision mode.
Tools
The tool list has not been reviewed yet.
Setup
Use the npm package @agent-infra/mcp-server-browser. For stdio, run the package directly; for SSE and Streamable HTTP, use npx and set the port parameter, which defaults to 8089. Configure the browser channel, CDP or WebSocket endpoint, browser executable path, output directory, proxy settings, and vision mode as needed.
Fit and risk
Not for
- Users seeking functions from the repository's other MCP servers
- Deployments requiring explicitly documented authentication or managed cloud hosting
- Environments that cannot grant an agent browser access
Required permissions
- Access to the target browser
- Permission to read browser screenshots when vision is enabled
- An environment supporting the DISPLAY variable for browser rendering, when needed
- Access to the specified CDP or WebSocket endpoint for remote connections
- Corresponding network, directory, or file access when configuring proxies, output directories, or browser executable paths
Risks and side effects
- Browser actions may affect pages and data in the active browser session
- Screenshots or page snapshots may contain sensitive information
- Misconfigured proxy, CDP, or WebSocket endpoints may broaden browser access
- The source does not document authentication configuration, so access control must be assessed separately
Troubleshooting
- Verify that the browser channel is chrome, edge, or firefox
- Check the CDP endpoint, WebSocket endpoint, or executable path
- When using screenshot mode, check DISPLAY and the browser rendering environment
- For SSE or Streamable HTTP, verify the port; the default is 8089
- Check proxy settings, the output directory, and target-browser availability
Use cases
Giving an MCP client access to a browser environment
Choosing between DOM/Aria snapshot access and screenshot-based browser vision
Connecting browser capabilities to multimodal agent workflows
Supported clients
Supported clients have not been confirmed yet.