M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
M

MCP Server Browser

Official
Browser access for MCP clients.
How to install ↓ Compare GitHub source repository ↗
Category
Browser #23 of 32
Stars
★ 39.3k Very popular
Transport
stdio (local process) · SSE · Streamable HTTP
Runtime
Node.js 22+
Credentials
No credential needed
License
Apache-2.0
Last commit
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.

Strongest · Maintenance 12/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
8/20
Maintenance
12/20
Documentation
8/20
Setup experience
10/20
Why each score
Reliability 8/20
The manifest declares an npm package, three transports, and runtime parameters, making a startup path plausible. However, the supplied material contains no server-specific tool list, initialization or tools-list handshake evidence, tests, CI, or error-handling documentation. It therefore does not establish that declared behavior matches implementation, and static calibration does not support a higher score.
Security and permissions 8/20
The evidence shows browser-control capability and accepts CDP, WebSocket, executable-path, proxy, and output-directory settings, with optional screenshots. These create browser-data, network-access, and side-effect risks. No credential handling, permission boundaries, data-flow disclosure, dangerous-operation confirmation, or isolation policy is documented. There is no evidence of a red-line malicious behavior, so this is not scored in the 0-4 range, but the missing controls require substantial deductions.
Maintenance 12/20
The repository is not archived, the README records multiple 2025 releases and feature updates, and Apache-2.0 licensing is stated, indicating ongoing project maintenance. However, this is primarily repository-level evidence; there is no server-specific release cadence, commit or test evidence, dependency-update policy, or security-response channel. The manifest also uses latest, reducing reproducibility, so the score is well below full marks.
Documentation 8/20
The manifest supplies the package identifier, transport modes, port default, and several runtime parameters; the repository README gives general context about browser operators and MCP. It does not document this server's tools, tool parameters, authentication, permission boundaries, limits, costs, platform prerequisites, or troubleshooting. The README is largely repository-wide rather than specific to the target server, warranting a low score.
Setup experience 10/20
An npm package and npx usage are indicated, with stdio, SSE, and streamable HTTP transports; the HTTP modes provide a default port of 8089. This gives a basic installation direction. Still, there is no complete client configuration example for this server, no Node/browser prerequisites, platform compatibility detail, or connection-verification procedure, and the SSE/HTTP modes require manual local port handling, limiting ease of setup.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkControls a browser

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

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

Setup

Before you start

Runtime：Node.js 22+

Other optional settings (1)
DISPLAY optional DISPLAY environment variable for browser rendering on Linux; usually set automatically in a desktop session (e.g. :0), no manual setup needed.

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.

Check that it works

Run npx @agent-infra/mcp-server-browser and check that its browser tools appear in your MCP client's tool list; issue a request to open a page and confirm a snapshot is returned to prove the connection works.

Troubleshooting

  1. Verify that the browser channel is chrome, edge, or firefox
  2. Check the CDP endpoint, WebSocket endpoint, or executable path
  3. When using screenshot mode, check DISPLAY and the browser rendering environment
  4. For SSE or Streamable HTTP, verify the port; the default is 8089
  5. Check proxy settings, the output directory, and target-browser availability

Things to try

Once connected, you can ask your AI assistant things like:

  • Open booking.com in the browser and search for hotels near LAX from September 1st to 6th
  • Take a screenshot of the current page using vision mode
  • Connect to Chrome via --cdp-endpoint and list the open tabs

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

Overview

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.

Similar servers

Compare with other MCP servers

More servers from this repository

UI-TARS Desktop MCP ServerUI-TARS Filesystem MCP ServerSearch MCP Server

Source revision 3ac2cb8d946d Data synced 2026-10-19 Read the FMRS scoring method