Navigation
MCP Browser: NeoForge-Powered Testing & Lightning Launches - MCP Implementation

MCP Browser: NeoForge-Powered Testing & Lightning Launches

Crush frontend testing with MCP Browser’s NeoForge server—where dev woes meet their match. Your code’s BFF for flawlessly fast launches. 🚀

Browser Automation
4.5(142 reviews)
213 saves
99 comments

This tool saved users approximately 5468 hours last month!

About MCP Browser

What is MCP Browser: NeoForge-Powered Testing & Lightning Launches?

MCP Browser is a high-performance headless browser interface built on the Model Control Protocol (MCP), designed to simplify automated testing and rapid deployment of web applications. Leveraging NeoForge's robust architecture, it combines real-time event streaming with intuitive browser automation, enabling seamless integration with AI-driven workflows. The toolset includes a web UI dashboard, WebSocket-driven live updates, and out-of-the-box support for Playwright-based testing—making it ideal for developers needing both precision and speed.

How to Use MCP Browser: NeoForge-Powered Testing & Lightning Launches?

Getting started involves three core steps: setup, testing, and scaling. Begin by cloning the repository and installing dependencies via uv (Astral's dependency manager). Once the virtual environment is activated, Playwright browsers are automatically provisioned. For lightweight testing, run ./simple_test.sh; full-stack validation (with Xvfb) uses ./test_local.sh. Production deployments leverage Docker Compose, where environment variables like MCP_SECRET and SERVER_PORT can be customized to match your infrastructure.

MCP Browser Features

Key Features of MCP Browser: NeoForge-Powered Testing & Lightning Launches?

  • Blazing-fast automation: Playwright's headless browsers execute scripts at machine-speed, with zero visual overhead
  • Real-time intelligence: WebSocket endpoints stream page events (navigation, DOM mutations, console logs) to subscribed clients in under 100ms
  • AI-native integration: Built-in MCP compatibility lets ML models directly control browser interactions
  • Operational clarity: The web UI provides live status dashboards and subscription tracking

Use Cases of MCP Browser: NeoForge-Powered Testing & Lightning Launches?

Common scenarios include:

  • Automating regression tests for dynamic SPAs
  • Powering real-time analytics dashboards with browser-rendered data extraction
  • Creating AI-driven bots for web scraping or customer service simulations
  • Validating cross-browser compatibility at scale

MCP Browser FAQ

FAQ: Tackling MCP Browser's Most Common Questions

Q: Can I use this without Docker?
A: Absolutely—local setups with Python 3.8+ and uv are fully supported. Docker is optional but recommended for production.

Q: How granular are event subscriptions?
A: You can filter by event type (e.g., page.load), DOM selectors, or even specific JavaScript execution contexts.

Q: Does it support headful mode?
A: Yes—simply pass --headed flags when launching browsers via Playwright's API.

Q: What’s the licensing model?
A: MIT-licensed for open-source projects; commercial deployments require a NeoForge API key (free tier available).

Content

MCP Browser

A headless browser interface for the Model Control Protocol (MCP).

Features

  • 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

Prerequisites

  • Python 3.13+
  • uv for dependency management
  • Docker (for containerized usage)

Local Development

Setup with uv

# Clone the repository
git clone https://github.com/yourusername/mcp-browser.git
cd mcp-browser

# Install dependencies
uv venv .venv
source .venv/bin/activate
uv pip install -e .

# Install Playwright browsers
python -m playwright install

Running Locally

For a simple test without Xvfb:

./simple_test.sh

For a full test with Xvfb (requires X11):

./test_local.sh

Docker Deployment

Build and run using Docker Compose:

# Set your MCP secret
export MCP_SECRET=your_secret_key

# Build and run
docker-compose up --build

Or use the provided script:

./run.sh

Configuration

The following environment variables can be set:

  • MCP_SECRET: Secret key for MCP authentication
  • SERVER_PORT: Port to run the server on (default: 7665)
  • PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD: Set to 1 to skip browser download and run in headless-only mode

API Endpoints

  • GET /: Web UI
  • GET /api/status: Get browser and MCP client status
  • WebSocket /ws: WebSocket endpoint for real-time communication
  • WebSocket /ws/browser/events: WebSocket endpoint for browser event subscriptions
  • GET /api/browser/subscribe: Subscribe to browser events
  • GET /api/browser/unsubscribe: Unsubscribe from browser events
  • GET /api/browser/subscriptions: List active event subscriptions

Event Subscriptions

The MCP Browser supports real-time event subscriptions via WebSockets. This allows clients to receive browser events as they happen, including:

  • Page events (navigation, load, error)
  • DOM events (mutations, changes)
  • Console events (logs, warnings, errors)
  • Network events (requests, responses, errors)

For detailed documentation and examples of the event subscription system, see:

License

MIT

Related MCP Servers & Clients