mcpField
M
MCP Browser Automation Server

MCP Browser Automation Server

Local
github.com/weir1Browser Automation0Updated 86w ago

About MCP Browser Automation Server

MCP Browser Automation Server provides browser-session controls through an HTTP API, including navigation, screenshots, clicks, and form entry. It is suited to automation tasks that also need live browser console logs.

Key features

  1. 01Create and close browser sessions
  2. 02Navigate to URLs
  3. 03Capture page or element screenshots
  4. 04Click elements and fill inputs
  5. 05Stream console logs over WebSocket

Use cases

  1. 01Automating browser navigation and form entry
  2. 02Capturing full-page or element screenshots
  3. 03Monitoring browser console output during a session

MCP support

The project is described as an MCP server, but the README documents browser controls through a REST API and WebSocket without specifying MCP tools or transport.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MCP Browser Automation Server

A simple but powerful browser automation server that allows you to control browsers, take screenshots, and monitor console logs through a REST API.

Features

  • Create browser sessions
  • Navigate to URLs
  • Take screenshots (full page or specific elements)
  • Click elements
  • Fill form inputs
  • Monitor console logs in real-time through WebSocket
  • Close sessions

Installation

  1. Clone this repository:
git clone https://github.com/weir1/mcp-browser-automation.git
cd mcp-browser-automation
  1. Create a virtual environment and activate it:
python -m venv venv
.\venv\Scripts\Activate
  1. Install dependencies:
pip install -r requirements.txt
  1. Install Playwright browsers:
playwright install

Usage

  1. Start the server:
python server.py

The server will start on http://localhost:8000

API Endpoints

Create a new session
POST /session/create
Response: { "session_id": "..." }
Navigate to a URL
POST /session/{session_id}/navigate?url=https://example.com
Take a screenshot
POST /session/{session_id}/screenshot?name=screenshot1&selector=.my-element

If selector is not provided, takes a full page screenshot.

Click an element
POST /session/{session_id}/click?selector=.my-button
Fill an input
POST /session/{session_id}/fill?selector=input[name="username"]&value=myuser
Monitor console logs
WebSocket /session/{session_id}/console
Close a session
POST /session/{session_id}/close

Example Usage with Python

import requests
import websockets
import asyncio
import json

# Create a session
response = requests.post("http://localhost:8000/session/create")
session_id = response.json()["session_id"]

# Navigate to a URL
requests.post(f"http://localhost:8000/session/{session_id}/navigate?url=https://example.com")

# Take a screenshot
response = requests.post(f"http://localhost:8000/session/{session_id}/screenshot?name=example")
with open("screenshot.png", "wb") as f:
    f.write(response.content)

# Monitor console logs
async def monitor_console():
    async with websockets.connect(f"ws://localhost:8000/session/{session_id}/console") as ws:
        while True:
            message = await ws.recv()
            print(json.loads(message))

asyncio.get_event_loop().run_until_complete(monitor_console())

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.