Isolated browser sessions for MCP clients.

Run independent Chromium contexts with explicit targets, deterministic ordering, and no shared current page.

stdio

{
  "mcpServers": {
    "browsermesh": {
      "command": "npx",
      "args": [
        "-y",
        "multi-agent-browser-mcp"
      ]
    }
  }
}

MCP configuration

Transport: MCP stdio
Browser engine: Chromium
Runtime: Local Node.js 22+

Clear responsibility boundary

The client reasons.
BrowserMesh executes.

Your AI client plans the workflow and chooses tools. BrowserMesh manages browser lifecycle, isolation, operation order, persistence, limits, and cleanup.

Read the architecture

Runtime guarantees

Contracts an MCP client can rely on during every browser workflow.

Separate identities

Every ready session owns a non-persistent Chromium context with its own cookies, storage, and pages.

1 session = 1 BrowserContext

Explicit targets

Page operations name both identifiers. A page reference from another session is rejected.

{ sessionId, pageId }

Predictable ordering

Operations serialize inside one session while independent sessions continue in parallel.

queue[sessionId]

Bounded results

Snapshots, text, screenshots, and observations report the limits applied to their output.

structured + bounded

First connection

From install to an isolated session.

BrowserMesh stays local. No hosted control plane or separate backend is required.

Open the setup guide

Install Chromium

bash

npx -y multi-agent-browser-mcp --install-browser

Connect your MCP client
bash
```
npx -y multi-agent-browser-mcp
```
Create a session
bash
```
browser_session_create
```