Browse Together MCP

What is Browse Together MCP?

Browse Together MCP is a Playwright browser proxy paired with an MCP server. It runs a headful browser on your desktop that you can control via HTTP API or through MCP clients like Claude Desktop, Cline, or Windsurf. Built with Deno and TypeScript, it lets you authenticate in a normal browser session and then use MCP tools inside that session for more powerful automation.

How to use Browse Together MCP?

Install Deno and Playwright browser binaries (npx playwright install). Start the browser service with deno task browser (listens on localhost:8888 by default). Configure your MCP client (e.g., in claude_desktop_config.json) to run deno run -A /path/to/mcp.ts. Then issue commands like goto, click, or fill through your MCP client, or send HTTP POST requests to /api/browser/:pageId.

Key features of Browse Together MCP

• Run with Chromium (default) or Firefox via BROWSER_TYPE env variable
• Single persistent browser session that stays alive while the service runs
• Named tabs let you control multiple pages using unique IDs
• Interact via simple JSON commands over HTTP or through any MCP client
• Full type safety with Zod validation of incoming commands
• Secure the HTTP endpoint with an optional API token
• Headful browser so you can manually log into services before automation

Use cases of Browse Together MCP

• Authenticated web scraping and data extraction inside your existing sessions
• Pull down documentation or content while you code, using MCP commands
• Automate form filling and clicks in a browser you can see and control
• Co-browsing scenarios where a human and an AI share the same browser session
• Testing web applications with real user‑like interactions

FAQ from Browse Together MCP

Is this “Computer Use” or “Operator”?

No. Browse Together MCP is a headful web browser that behaves like a normal human‑controlled browser, not a Computer Use / Operator service. You can get screenshots and pull docs, but the focus is on remote control of a browser session, not autonomous AI agent actions.

What runtime and dependencies do I need?

You need Deno installed (see deno.land installation guide) and Playwright browser binaries installed via npx playwright install. Currently only macOS is supported, but the project can be extended to other platforms with minor changes.

Where does browser data live?

All browser state (sessions, cookies, local storage) is kept in a single persistent Playwright browser instance that runs for the lifetime of the service. Data does not persist across restarts unless you configure that yourself.

What transports and authentication are available?

The MCP server communicates over STDIO (and optionally SSE via FastMCP). The HTTP API listens on a local port (default 8888) and can be secured by setting an API token in environment variables.

Are there any known limitations?

The project is currently tested only on macOS. It does not provide Computer Use / Operator functionality—it is a remote control tool for a real browser driven by MCP or HTTP commands.