brawsr

io.github.brawsrPublished by GitHub account brawsrv0.2.0Updated Oct 24, 2026

Browser sessions, checkpoints, rewind, fork, lineage, and lifecycle tools for brawsr.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Local MCP bridge for brawsr browser sessions, letting an assistant create, checkpoint, rewind and fork sessions and track their lineage.

What you can do
Create, list, inspect, label and close browser sessions, including bulk close and CDP URL retrieval while attachable. Create, get, list and delete checkpoints, and list rewindable checkpoints. Rewind a session or fork it into an independent child session. Inspect session activity, lineage and fork trees. Look up or wait on long-running operations.
When to use it
Useful when you work with brawsr browser sessions and want an assistant to manage their lifecycle, take checkpoints, roll back to an earlier state, or branch a session for parallel exploration.
Requirements
Runs locally over stdio as an npm package, requiring Node.js 22 or newer. A brawsr API key must be supplied in the BRAWSR_API_KEY environment variable. Optional BRAWSR_BASE_URL overrides the built-in production endpoint, and BRAWSR_MCP_TIMEOUT_MS sets the default operation wait. Network access to the brawsr API is needed.
Before you install
The server requires the BRAWSR_API_KEY secret and talks to the brawsr API. Tools write and delete data: sessions can be closed, labels changed, checkpoints deleted, and rewind or fork changes browser state. Rewind does not undo remote website side effects and makes old CDP handles stale. CDP URLs are sensitive outputs; the server does not proxy CDP and never returns the Authorization header.

Installation

In SourceWeft

  1. Open brawsr in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

brawsr MCP server

The authenticated local MCP bridge for brawsr browser sessions, checkpoints, rewind, and fork. It uses the official packaged @brawsr/sdk; it does not duplicate API models, poll orchestration, or browser/CDP behavior.

The v0.2 transport is local stdio and requires Node.js 22+.

Install and configure

MCP clients spawn the server locally. Pin the package version in client configuration so an MCP client restart cannot silently select a newer release:

json
{  "mcpServers": {    "brawsr": {      "command": "npx",      "args": ["-y", "@brawsr/[email protected]"],      "env": {        "BRAWSR_API_KEY": "your-brawsr-api-key"      }    }  }}

The npm package includes the official @brawsr/sdk; no second package install is required. BRAWSR_API_KEY is the only required environment variable. The production endpoint https://api.brawsr.io is built in.

For local development or another deployment, BRAWSR_BASE_URL may explicitly override that endpoint. BRAWSR_MCP_TIMEOUT_MS optionally changes the default bounded operation wait from 30 seconds and accepts an integer from 1 through 300000.

The API key is never a tool argument or result. Standard output is reserved for MCP protocol messages. Redacted lifecycle diagnostics use standard error. A direct shell launch uses the same executable:

bash
BRAWSR_API_KEY=... npx -y @brawsr/[email protected]

Tools

  • brawsr_create_session, brawsr_list_sessions, brawsr_get_session, brawsr_update_session_label, brawsr_close_session
  • brawsr_close_sessions
  • brawsr_create_checkpoint, brawsr_get_checkpoint, brawsr_list_checkpoints, brawsr_delete_checkpoint
  • brawsr_list_rewindable_checkpoints, brawsr_list_session_activity, brawsr_get_session_lineage
  • brawsr_rewind, brawsr_fork
  • brawsr_get_operation, brawsr_wait_operation

Session creation accepts an optional display_label. The same label can be changed or cleared with one brawsr_update_session_label call. Session lists are newest-first, bounded, and may include retained closed or expired sessions. brawsr_get_session includes a CDP URL only while the session is attachable.

brawsr_list_checkpoints is capture history: it can include deleted captures for audit and dashboard views. Use brawsr_list_rewindable_checkpoints when choosing a valid rewind or fork target. Lineage returns one session, its optional parent fork edge, and one bounded page of direct children; callers can follow child session IDs to browse a nested fork tree. Pagination cursors are opaque and may be passed back unchanged.

Checkpoint, rewind, and fork are one high-level tool call. The packaged SDK hides ordinary 202 polling. Rewind returns as soon as its result is CDP-usable; the operation may finish bounded post-restore work in the background. A timeout stops only local waiting and returns the operation/idempotency recovery fields; server work continues.

Fork children are independent peer sessions, not implicit winners or losers. There is no browser-state merge and no automatic sibling cleanup. Rewind restores browser/client state, not remote website side effects, and makes old CDP/browser handles stale. Long-lived WSS/SSE/WebRTC streams may need application-level reconnection.

CDP URLs are sensitive structured outputs. The MCP server never returns the Authorization header. Use the ordinary SDK or a supported framework to attach; the MCP server does not proxy CDP.

Remote Streamable HTTP, OAuth, hosted multi-tenancy, legacy HTTP+SSE, and resumable MCP sessions are deferred beyond the local v0.2 stdio boundary.

Development

bash
npm cinpm run verify

Release archives are built reproducibly with the pinned Node 24 and npm 11.5.1 toolchain. CI also exercises the server and its real MCP client boundary on Node 22 and Node 24. npm hosts the executable package; the official MCP Registry hosts discovery metadata for io.github.brawsr/brawsr.

Source: README.md at commit c6aa3a6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts