MCP Browser

Name: MCP Browser
Author: neoforge-dev

@neoforge-dev

Repository

About MCP Browser

NeoForge Browser MCP server - used to test the frontend

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-browser": {
      "command": "uv",
      "args": [
        "venv",
        ".venv"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Browser?

MCP Browser is a headless browser interface for the Model Control Protocol (MCP) that uses Playwright for browser automation. It provides a Web UI for browser interaction and WebSocket communication for real-time updates, designed for integration with AI agents.

How to use MCP Browser?

Install via one-line command or manually with Python 3.13+ and uv. Run locally using ./simple_test.sh or ./test_local.sh, or deploy with Docker Compose after setting MCP_SECRET. Configure via environment variables like MCP_SECRET, SERVER_PORT, and PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD.

Key features of MCP Browser

Headless browser automation using Playwright
Web UI for browser interaction
WebSocket communication for real-time updates
Real-time browser event subscription system
Integration with MCP for AI agents

Use cases of MCP Browser

AI agents automating web browsing tasks
Real-time monitoring of browser events for testing
Headless browser control through MCP protocols
Live DOM, console, and network event inspection

FAQ from MCP Browser

What are the prerequisites for MCP Browser?

Python 3.13+, uv for dependency management, and Docker (for containerized usage). XQuartz (X11) is required for visualization on Mac.

How do I install MCP Browser?

Use the one-line installation command curl -sSL https://raw.githubusercontent.com/neoforge-dev/mcp-browser/main/install_one_line.sh | bash or clone the repo and run ./install.sh.

What environment variables does MCP Browser use?

MCP_SECRET for authentication, SERVER_PORT (default 7665), and PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD to skip browser download for headless-only mode.

How does real-time browser event subscription work?

Clients can subscribe to browser events via WebSocket endpoints like /ws/browser/events and receive page, DOM, console, and network events as they happen.

What APIs does MCP Browser expose?

It exposes a Web UI at GET /, a status endpoint at GET /api/status, WebSocket endpoints for real-time communication, and endpoints for subscribing and unsubscribing to browser events.