Manages browser sessions, checkpoints, rewinds, and forks using the brawsr SDK.
Also known as brawsr/mcp-server, mcp-server, @brawsr/mcp-server
- Stars
- 0
- Tools
- 1
- Downloads, 30 days
- 159
- Latest version
- 0.2.0
- Last commit
- Nov 13, 2026
- License
- Apache-2.0
What is brawsr MCP?
brawsr manages browser sessions, checkpoints, rewinds, and forks using the brawsr SDK. It exposes 1 tool, such as brawsr_close_sessions.
Summary generated from the project's README
About brawsr MCP server
Managing browser sessions, checkpoints, and state forks through an AI client is what brawsr enables for developers. This local MCP server acts as an authenticated bridge using the official @brawsr/sdk to control browser environments via stdio transport. It requires Node.js 22 or higher and a BRAWSR_API_KEY environment variable to function.
Users can interact with the browser through specific tools like brawsr_create_session, brawsr_rewind, and brawsr_fork. The server handles complex operations by hiding polling logic, allowing for direct commands to create checkpoints or list session lineage. While it connects to the production endpoint by default, developers can override the BRAWSR_BASE_URL or adjust the BRAWSR_MCP_TIMEOUT_MS for longer operations.
This implementation focuses on local execution and does not proxy CDP connections or handle remote streamable HTTP. It provides structured access to session history and lineage, enabling a nested fork tree structure where children sessions exist as independent peers. This setup is designed for developers who need precise control over browser state without duplicating existing API models or orchestration behavior.
What you can do with it
- 1Reverting browser stateAsk the AI to restore a browser session to a specific previous point in time.
- 2Branching browser workflowsInstruct the client to create a new independent session based on an existing one.
- 3Auditing session historyRequest a list of all captured checkpoints to review past browser activity.
- 4Navigating session hierarchiesTrace the relationship between a parent session and its various child forks.
Written from the project's README. Every use case is checked against a quote from it.
How to install brawsr MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall brawsr MCP in Claude Code
$ claude mcp add --env 'BRAWSR_API_KEY=<YOUR_BRAWSR_API_KEY>' mcp-server -- npx -y @brawsr/mcp-serverInstall brawsr MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@brawsr/mcp-server"
],
"env": {
"BRAWSR_API_KEY": "<YOUR_BRAWSR_API_KEY>"
}
}
}
}Install brawsr MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@brawsr/mcp-server"
],
"env": {
"BRAWSR_API_KEY": "<YOUR_BRAWSR_API_KEY>"
}
}
}
}Install brawsr MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@brawsr/mcp-server"],"env":{"BRAWSR_API_KEY":"<YOUR_BRAWSR_API_KEY>"}}'Install brawsr MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@brawsr/mcp-server"
],
"env": {
"BRAWSR_API_KEY": "<YOUR_BRAWSR_API_KEY>"
}
}
}
}Install brawsr MCP in Codex
$ codex mcp add mcp-server --env 'BRAWSR_API_KEY=<YOUR_BRAWSR_API_KEY>' -- npx -y @brawsr/mcp-serverInstall brawsr MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@brawsr/mcp-server"] [mcp_servers.mcp-server.env] BRAWSR_API_KEY = "<YOUR_BRAWSR_API_KEY>"
Install brawsr MCP in Gemini CLI
$ gemini mcp add -s user -e 'BRAWSR_API_KEY=<YOUR_BRAWSR_API_KEY>' mcp-server npx -- -y @brawsr/mcp-serverInstall brawsr MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@brawsr/mcp-server"
],
"env": {
"BRAWSR_API_KEY": "<YOUR_BRAWSR_API_KEY>"
}
}
}
}brawsr MCP tools 1
Detected from the READMEbrawsr_close_sessions
| brawsr_close_sessions | — |
Configuration
BRAWSR_API_KEYRequiredSecretAPI key for the brawsr project used by this MCP server.
BRAWSR_BASE_URLOptional explicit API endpoint override for local development or another deployment.
BRAWSR_MCP_TIMEOUT_MSOptional default lifecycle wait in milliseconds, from 1 through 300000.
| Name | Description | |
|---|---|---|
| BRAWSR_API_KEY | API key for the brawsr project used by this MCP server. | RequiredSecret |
| BRAWSR_BASE_URL | Optional explicit API endpoint override for local development or another deployment. | |
| BRAWSR_MCP_TIMEOUT_MS | Optional default lifecycle wait in milliseconds, from 1 through 300000. |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubbrawsr 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:
{
"mcpServers": {
"brawsr": {
"command": "npx",
"args": ["-y", "@brawsr/mcp-server@0.2.0"],
"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:
BRAWSR_API_KEY=... npx -y @brawsr/mcp-server@0.2.0
Tools
brawsr_create_session,brawsr_list_sessions,brawsr_get_session,brawsr_update_session_label,brawsr_close_sessionbrawsr_close_sessionsbrawsr_create_checkpoint,brawsr_get_checkpoint,brawsr_list_checkpoints,brawsr_delete_checkpointbrawsr_list_rewindable_checkpoints,brawsr_list_session_activity,brawsr_get_session_lineagebrawsr_rewind,brawsr_forkbrawsr_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
npm ci
npm 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.
brawsr MCP questions
How do I add brawsr MCP to Claude Code?
Run claude mcp add --env 'BRAWSR_API_KEY=<YOUR_BRAWSR_API_KEY>' mcp-server -- npx -y @brawsr/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add brawsr MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does brawsr MCP provide?
It exposes 1 tool, including brawsr_close_sessions.
What environment variables are required to run the brawsr MCP server?
The only required environment variable is BRAWSR_API_KEY.
Can I change the default operation timeout?
Yes, you can use the BRAWSR_MCP_TIMEOUT_MS variable to set a custom timeout between 1 and 300,000 milliseconds.
Does the server proxy CDP connections?
No, the MCP server does not proxy CDP; you must use the SDK or a supported framework to attach using the provided CDP URLs.
What happens to browser state during a rewind operation?
Rewind restores the browser and client state, but it does not restore remote website side effects and will make old CDP/browser handles stale.