Log inSubmit server
Browser Use logo

Browser Use

Controls a real Chrome browser for agent-driven navigation, form filling, extraction, and web tasks.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Browser Use

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for browser-use, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The browser-use MCP server lets an AI agent control a real Chrome browser to navigate websites, complete forms, and extract information. Browser Use supports local browsers, its cloud browser, and existing remote browsers over CDP, with browser actions driven by an agent. Reach for it when a task requires interacting with websites rather than only calling structured APIs.

Use cases

  • Complete multi-step web forms
  • Extract information from websites
  • Book appointments or tests through browser workflows
  • Navigate sites that lack a structured API

Key features

  • Real Chrome browser control
  • Multi-step website navigation
  • Form filling and date selection
  • Web-page data extraction
  • Local, cloud, and CDP browser support
  • 31 documented browser actions in the Anthropic integration

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

24/24 checks healthy over the last 73d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 0Medium 0Low 1

Scanned 17d ago via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars118kStargazers on the source repository.
Last commit2d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Browser Use works

What the browser-use MCP server does

The browser-use MCP server gives an AI agent access to browser automation for tasks that require visual or interactive work on the web. It can open pages, follow navigation flows, enter information into forms, select dates and times, retrieve page data, and complete multi-step tasks such as booking a driving test or finding information in a repository.

The project is aimed at agents that need to operate websites as a person would. That makes it a fit for sites without a suitable public API, workflows that depend on browser state, and tasks involving several pages or interaction steps.

How it works

The browser-use MCP server acts as a browser driver for an AI agent. Browser actions are provided to the agent, which determines the next interaction from the current page and the requested task. The underlying browser can run locally, use Browser Use Cloud, or connect to an existing remote browser through CDP in the documented integrations.

Browser Use also exposes an open-source agent for Python and supports TypeScript. Its documented Python path uses an LLM, an agent instance, and a local or cloud browser. The project also documents an Anthropic SDK integration that supplies browser actions and can add Bash for processing data or writing files on the SDK host.

Setup and configuration

The browser-use MCP server's broader project setup depends on the execution path. The Python library requires Python 3.11 or newer and can be installed with uv add browser-use. The example configuration uses OPENAI_API_KEY; BROWSER_USE_API_KEY is needed when using the BU2 model or Browser Use Cloud. The documented Anthropic integration requires an Anthropic SDK version that includes the browser tool, and Bash support requires Linux or macOS, or WSL on Windows.

The repository also documents a CLI workflow for installing or upgrading Browser Use with uv, registering its skill, and connecting it to a browser. That path names Claude Code, Codex, Hermes, and OpenClaw as possible agent environments.

Tools and capabilities

The browser-use MCP server supports the browser action set used by Browser Use. Supported task categories include:

  • Navigating websites and following multi-step flows
  • Filling out web forms
  • Selecting dates and times
  • Extracting information from pages
  • Handling CAPTCHA steps in demonstrated workflows
  • Using local, cloud, or remote browser targets, depending on the integration

The project can also pair browser control with Bash in its Anthropic SDK integration for local data processing and file output.

Limitations and notes

Browser automation depends on the target site's layout, access controls, login state, and other runtime conditions. Cloud browsers and the BU2 model require a Browser Use API key, while the local Python example uses an OpenAI API key. Bash integration is limited to hosts with /bin/bash, with WSL recommended for Windows users.

Consult the repository and linked documentation for those details before deploying the browser-use MCP server.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Browser Use

browser-use is an MCP server that connects AI agents to a real Chrome browser and exposes browser actions for navigation, interaction, form filling, and data extraction. It supports local, cloud, and remote browsers over CDP in documented integrations, allowing agents to complete multi-step website tasks.

Install the related Python package with `uv add browser-use` when using the documented Python library path.

The Python example requires `OPENAI_API_KEY` for the OpenAI model. `BROWSER_USE_API_KEY` is required for the BU2 model or Browser Use Cloud. Requirements may differ for other integrations, including the Anthropic SDK path.

Yes, Claude Code is named as an agent environment in the repository's CLI setup instructions. The same instructions also mention Codex, Hermes, and OpenClaw, while the documented Anthropic integration requires an SDK version that includes its browser tool.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBrowser Use AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/browser-use?style=directory)](https://allmcps.com/mcp/browser-use)
HTML Embed
<a href="https://allmcps.com/mcp/browser-use"><img src="https://allmcps.com/api/badge/browser-use?style=directory" alt="Browser Use on AllMCPs" /></a>