browser-use-mcp-server

MCP.Pizza Chef: co-browser

The browser-use-mcp-server is an MCP server that enables AI agents to control and automate web browsers through the browser-use library. It leverages Playwright for browser automation and integrates seamlessly with MCP clients, allowing real-time web interaction from environments like Cursor. This server supports multi-browser management and simplifies workflows by enabling AI-driven web navigation and data extraction.

Use This MCP server To

Automate web browsing tasks via AI agents Enable AI to interact with web pages in real time Control multiple browsers for parallel web automation Extract structured data from websites dynamically Integrate browser control into AI-enhanced workflows Test web applications through scripted browser interactions Simulate user browsing behavior for research or testing

README

browser-use-mcp-server

Twitter URL Discord PyPI version

An MCP server that enables AI agents to control web browsers using browser-use.

🔗 Managing multiple MCP servers? Simplify your development workflow with agent-browser

Prerequisites

# Install prerequisites
curl -LsSf https://astral.sh/uv/install.sh | sh
uv tool install mcp-proxy
uv tool update-shell

Environment

Create a .env file:

OPENAI_API_KEY=your-api-key
CHROME_PATH=optional/path/to/chrome
PATIENT=false  # Set to true if API calls should wait for task completion

Installation

# Install dependencies
uv sync
uv pip install playwright
uv run playwright install --with-deps --no-shell chromium

Usage

SSE Mode

# Run directly from source
uv run server --port 8000

stdio Mode

# 1. Build and install globally
uv build
uv tool uninstall browser-use-mcp-server 2>/dev/null || true
uv tool install dist/browser_use_mcp_server-*.whl

# 2. Run with stdio transport
browser-use-mcp-server run server --port 8000 --stdio --proxy-port 9000

Client Configuration

SSE Mode Client Configuration

{
  "mcpServers": {
    "browser-use-mcp-server": {
      "url": "http://localhost:8000/sse"
    }
  }
}

stdio Mode Client Configuration

{
  "mcpServers": {
    "browser-server": {
      "command": "browser-use-mcp-server",
      "args": [
        "run",
        "server",
        "--port",
        "8000",
        "--stdio",
        "--proxy-port",
        "9000"
      ],
      "env": {
        "OPENAI_API_KEY": "your-api-key"
      }
    }
  }
}

Config Locations

Client Configuration Path
Cursor ./.cursor/mcp.json
Windsurf ~/.codeium/windsurf/mcp_config.json
Claude (Mac) ~/Library/Application Support/Claude/claude_desktop_config.json
Claude (Windows) %APPDATA%\Claude\claude_desktop_config.json

Features

  • Browser Automation: Control browsers through AI agents
  • Dual Transport: Support for both SSE and stdio protocols
  • VNC Streaming: Watch browser automation in real-time
  • Async Tasks: Execute browser operations asynchronously

Local Development

To develop and test the package locally:

  1. Build a distributable wheel:

    # From the project root directory
    uv build
  2. Install it as a global tool:

    uv tool uninstall browser-use-mcp-server 2>/dev/null || true
    uv tool install dist/browser_use_mcp_server-*.whl
  3. Run from any directory:

    # Set your OpenAI API key for the current session
    export OPENAI_API_KEY=your-api-key-here
    
    # Or provide it inline for a one-time run
    OPENAI_API_KEY=your-api-key-here browser-use-mcp-server run server --port 8000 --stdio --proxy-port 9000
  4. After making changes, rebuild and reinstall:

    uv build
    uv tool uninstall browser-use-mcp-server
    uv tool install dist/browser_use_mcp_server-*.whl

Docker

Using Docker provides a consistent and isolated environment for running the server.

# Build the Docker image
docker build -t browser-use-mcp-server .

# Run the container with the default VNC password ("browser-use")
# --rm ensures the container is automatically removed when it stops
# -p 8000:8000 maps the server port
# -p 5900:5900 maps the VNC port
docker run --rm -p8000:8000 -p5900:5900 browser-use-mcp-server

# Run with a custom VNC password read from a file
# Create a file (e.g., vnc_password.txt) containing only your desired password
echo "your-secure-password" > vnc_password.txt
# Mount the password file as a secret inside the container
docker run --rm -p8000:8000 -p5900:5900 \
  -v $(pwd)/vnc_password.txt:/run/secrets/vnc_password:ro \
  browser-use-mcp-server

Note: The :ro flag in the volume mount (-v) makes the password file read-only inside the container for added security.

VNC Viewer

# Browser-based viewer
git clone https://github.com/novnc/noVNC
cd noVNC
./utils/novnc_proxy --vnc localhost:5900

Default password: browser-use (unless overridden using the custom password method)

VNC Screenshot

VNC Screenshot

Example

Try asking your AI:

open https://news.ycombinator.com and return the top ranked article

Support

For issues or inquiries: cobrowser.xyz

Star History

Star History Chart

browser-use-mcp-server FAQ

How do I install browser-use-mcp-server?
Install using Python package manager uv and ensure Playwright and mcp-proxy are set up as prerequisites.
What browser automation technology does this server use?
It uses Playwright for robust, cross-browser automation.
Can this server manage multiple browsers simultaneously?
Yes, it supports controlling multiple browser instances concurrently.
Is this server compatible with different MCP clients?
Yes, it integrates with any MCP client that supports the MCP protocol.
What environments can I use this server in?
It is designed for environments like Cursor and other MCP host platforms.
Does it support real-time web interaction?
Yes, it enables AI agents to browse and interact with web pages in real time.
How does it simplify AI-driven web automation?
By exposing browser control as an MCP server, it standardizes and streamlines AI interactions with the web.
Are there any dependencies I should be aware of?
Yes, it requires uv, Playwright, and mcp-proxy for full functionality.