Browse Together MCP

A project integrating a Playwright - based browser proxy and MCP service, supporting browser session control via HTTP API or MCP client

Browser automation Developer tools #Browser control #MCP integration #Collaborative browsing #HTTP proxy .TypeScript

rating : 2.5 points

downloads : 18

update time : 2025-04-28

What is the Browse Together MCP Server?

The Browse Together MCP Server is a tool that integrates the Playwright browser and the MCP framework, allowing users to remotely control a continuously running browser session via HTTP API or MCP client. It supports functions such as multi - page operations, screenshot capture, and form filling.

How to use the Browse Together MCP Server?

You can start the server via the command line and use the HTTP API or MCP client to send instructions to control the browser. For example, you can navigate to a specific web page or click a button.

Applicable scenarios

Suitable for scenarios that require multi - person collaborative web browsing, automated testing, document downloading, or form filling.

Main Features

Multi - browser supportSupports Chromium and Firefox browsers to meet different needs.

Persistent browser sessionA single browser instance remains running throughout the entire service lifecycle.

Named page managementManage multiple pages (tabs) via a unique ID for easy multitasking.

HTTP API integrationProvides a simple and easy - to - use JSON command interface to control the browser easily via HTTP.

MCP protocol supportCompatible with MCP clients such as Cline and Windsurf to enhance the user experience.

Advantages and Limitations

Advantages

Easy to integrate into existing systems

Supports multiple browsers and operating systems

Powerful HTTP API and MCP toolset

High security, supports API token protection

Limitations

Currently only supports the Mac OS platform, additional adaptation is required for other platforms

There may be some delay in complex interactions

How to Use

Install dependencies

Ensure that Playwright and Deno are installed.

Start the server

Use Deno to run the browser and the service.

Configure the MCP client

Add server configuration in the MCP client.

Usage Examples

Case 1: Team collaborative developmentTeam members can view and edit the same web page simultaneously to improve collaboration efficiency.

Case 2: Automated form fillingAutomatically complete form filling and submission to reduce repetitive work.

Frequently Asked Questions

Does it support cross - platform operation?

How to ensure data security?

Does it support custom browser types?

Related Resources

Official documentation

Detailed usage guide and technical documentation.

GitHub repository

Source code and the latest version release.

Quick start video

A step - by - step guide to setting up and using Browse Together MCP.

🚀 Playwright Browser Proxy with MCP Server

This project allows you to run a Playwright browser and an MCP server on your desktop. You can start a headed browser (for human interaction) along with a corresponding MCP server, which can control the browser via HTTP API or the MCP server itself.

This project offers two complementary services for browser automation and collaborative browsing:

Browser Proxy Service: Controls a persistent Playwright browser instance via HTTP. You can log in to the services you use as usual.
MCP Server: Exposes browser functions to MCP clients (such as Claude Desktop) through the FastMCP framework. It can run within the authentication session you provide, giving your MCP commands more permissions and uses.

Both are built with Deno and TypeScript and work seamlessly together.

✨ Features

Multi-browser Support: Supports Chromium (default) or Firefox.
Persistent Browser Session: A browser instance runs throughout the service lifecycle.
Page Management: Lists all active browser pages and closes specific pages.
Content Manipulation: Fills form fields, clicks elements, retrieves page HTML content, and executes fetch requests in the browser context.

📚 Documentation

This project describes incremental planning steps through a series of documents:

Initial Design Decisions (Note: The project structure description may be outdated)
Overview of Browser Proxy Service (Multi-session - History)
Single-session Architecture Refactoring
Type Safety Plan (Zod)
Page Resilience Plan
Libraries Used
Testing Strategy
Configuration
Security Considerations
Deno Best Practices
MCP Server Implementation Plan
FastMCP Refactoring

Some of these steps may be outdated or no longer relevant but are included as a reference to understand how the project was built.

For more information about our local Sandy, Utah Vibe Coding Group, visit vibe-coders.org.

📦 Installation

Development

Run Browser Proxy: deno task browser
Run MCP Server: deno task mcp
Format Code: deno fmt
Check Dependencies: deno check --all browser.ts mcp.ts types.ts

🔧 Technical Details

Architecture

+----------------+      +--------------+      +------------------+
|                |      |              |      |                  |
| Cline/LLM      | ---- | MCP Server   | ---- | Browser Service  |
| (MCP Client)   |      | (mcp.ts)     | HTTP | (browser.ts)     |
|                |      |              |      |                  |
+----------------+      +--------------+      +------------------+
                               |                       |
                          FastMCP API            Playwright API
                               |                       |
                           Standard Input/Output Stream       Chromium Browser

The system works as follows:

The Browser Service (browser.ts) manages a persistent Chromium browser instance using Playwright.
The MCP Server (mcp.ts) provides a standard MCP interface using FastMCP.
The MCP server forwards commands to the browser service via HTTP.
MCP Clients such as Claude Desktop can use all browser functions through simple tool calls.