Browser Use Rs

What BB-fat/browser-use-rs MCP server does

BB-fat/browser-use-rs MCP server connects AI-driven workflows to Chrome or Chromium through the Chrome DevTools Protocol. It is implemented in Rust and provides a built-in Model Context Protocol server for browser automation.

The available browser operations cover common page interaction tasks: opening a URL, clicking elements, entering text, taking screenshots, extracting page content, and inspecting the DOM. DOM extraction includes indexed interactive elements, giving an agent a compact way to identify controls and refer to them by number. Elements can also be targeted with CSS selectors.

This fits the 📂 Browser Automation category for workflows where an agent must operate a browser rather than call a website-specific API. It is intended for developers who want a small Rust-based runtime and already have Chrome or Chromium available.

How it works

The library controls a browser session through CDP. A session can launch a browser, navigate to a URL, and extract the current DOM. The MCP server exposes the same general browser capabilities to an MCP client so an agent can request actions and receive browser results.

Interactive elements in extracted DOM output receive numeric indexes. An automation flow can use those indexes for element targeting, or use CSS selectors when the page structure and selector are known. Browser session management is thread-safe according to the project documentation.

The repository includes a command for running the MCP server in headless mode and an option for launching a visible browser. The visible mode is useful when a developer needs to observe the automated session while testing.

Setup and configuration

BB-fat/browser-use-rs MCP server requires Rust 1.70 or newer and an installed Chrome or Chromium browser. The project is distributed as a Rust library and can be added with Cargo. The MCP server can be started with cargo run --bin mcp-server for headless operation.

Add --headed to run with a visible browser window:

cargo run --bin mcp-server -- --headed

Browser availability is therefore a required part of the local setup.

Tools and capabilities

BB-fat/browser-use-rs MCP server supports these documented capabilities:

• Navigate to web pages.
• Click browser elements.
• Enter text into page controls.
• Capture screenshots.
• Extract page content.
• Extract the DOM with indexed interactive elements.
• Select targets with CSS selectors or numeric indexes.
• Maintain browser sessions with thread-safe session management.

The project describes the implementation as having no Node.js dependency and using a lightweight Rust runtime. Its direct CDP approach is relevant when a deployment should avoid a JavaScript browser-automation stack.

Limitations and notes

A Chrome or Chromium installation is required; the project does not describe a bundled browser. The documented runtime requirement is Rust 1.70 or newer.

The server is designed around CDP-compatible Chrome-family browsers. Compatibility with other browser engines is not stated. The repository is licensed under MIT and acknowledges inspiration from another browser MCP implementation.