BrowserMesh

Run many browser sessions at once, fully isolated from each other, from one MCP server.

Every other browser MCP server gives your AI client one browser with a current tab. BrowserMesh gives it as many independent sessions as the task needs — each with its own cookies, storage, and authentication — running in parallel. Test checkout as a customer while an admin session verifies the order, in one conversation, without either seeing the other's state.

• Documentation
• Getting started
• MCP tool reference

External AI client
        |
     MCP stdio
        |
BrowserMesh runtime
   |         |         |
Session A  Session B  Session C
Context A  Context B  Context C

The external client reasons and plans. BrowserMesh executes browser operations, enforces isolation, orders work within each session, and returns structured results.

Works with Claude Code, Claude Desktop, Codex, Cursor, Windsurf, Qwen, and any other MCP-compatible client.

Quick start

Claude Code:

claude mcp add browsermesh -- npx -y browsermesh

Any other client, in its MCP configuration file:

{
  "mcpServers": {
    "browsermesh": {
      "command": "npx",
      "args": ["-y", "browsermesh"]
    }
  }
}

That is the whole setup. On its first start BrowserMesh downloads the Chromium build it uses, so there is no separate install step. Pass --no-auto-install to manage the browser yourself, in which case MCP discovery still works and browser_session_create returns an actionable BROWSER_ERROR explaining what to run.

Then ask for the work in plain language:

Test the checkout flow as a buyer and confirm the order appeared, as an admin, at the same time.

The client creates one session per role on its own. BrowserMesh also publishes a parallel_roles prompt that spells the workflow out, so a client can offer it directly.

Check an installation without starting the protocol:

npx -y browsermesh --doctor

Chromium and BrowserMesh remain on your machine. There is no hosted BrowserMesh service.

Renamed in 0.2. The npm package was multi-agent-browser-mcp and is now browsermesh, matching the name everything else already used. Change args to ["-y", "browsermesh"]; nothing else moves.

v0.1 architecture

BrowserMesh v0.1 is intentionally small: one local Node.js process, one Chromium process, and one non-persistent BrowserContext for every ready session.

It provides:

• explicit session and page addressing;
• isolated browser contexts and page ownership checks;
• navigation, inspection, interaction, waits, capture, and persistence;
• per-session serialization with parallel execution across independent sessions;
• bounded timeouts, structured errors, graceful shutdown, and resource cleanup;
• MCP stdio integration with deterministic integration and end-to-end tests.

BrowserMesh is a browser runtime, not an internal agent framework, LLM orchestrator, message bus, Playwright fork, browser GUI, or interactive shell.

How it is normally used

1. Configure BrowserMesh once in an MCP-compatible AI client.
2. The client starts BrowserMesh over stdio and discovers its tools.
3. Describe the browser task in natural language.
4. The client creates the required sessions and chooses the tools to invoke.
5. BrowserMesh executes the operations and returns structured results.

Use a separate session for each user, account, role, authentication state, or independent parallel workflow. BrowserMesh tools are normally selected by the external client rather than called by hand.

Build from source

BrowserMesh v0.1 targets Node.js 24 and supports Node.js 22 as its minimum supported major version.

Clone the repository and run:

npm install
npx playwright install chromium

... [View full README on GitHub](https://github.com/scrolldynasty/multi-agent-browser-mcp#readme)