Log inSubmit server
Sendblue Browser MCP logo

Sendblue Browser MCP

Runs a stealth-patched Chromium daemon with MCP tools for navigation, screenshots, JavaScript evaluation, sessions, and CDP access.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Sendblue Browser MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sendblue-browser-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "sendblue-browser-mcp@0.2.3"
      ],
      "env": {
        "BROWSER_USE_API_KEY": "YOUR_VALUE_HERE",
        "BROWSER_USE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 13 tools correctly (24d ago).

Overview

The sendblue-browser-mcp MCP server connects AI agents to a standalone stealth-patched Chromium daemon through an HTTP API. Its MCP wrapper exposes browser health checks, named session management, navigation, screenshots, page scripts, cookies, console messages, CDP URLs, and session cleanup. Use it when agents need persistent browser profiles, shared sessions, or direct access to a browser that can also be driven by Playwright, Puppeteer, or other CDP clients.

Use cases

  • Reuse authenticated browser sessions across agent runs
  • Capture screenshots after browser navigation
  • Run JavaScript in an active page
  • Debug isolated browser workflows concurrently
  • Attach Playwright or Puppeteer through CDP

Key features

  • Named persistent and isolated browser sessions
  • Navigation and PNG screenshot tools
  • In-page JavaScript evaluation
  • Cookie and console inspection
  • Optional CDP attachment
  • Bearer-token HTTP API

Tools13

What Sendblue Browser MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

11/11 checks healthy over the last 62d

What it can do

From the 13 tools this server returned when we ran it.

Runs commands · 1Can delete or modify data · 2Handles credentials · 3Makes network requests · 6Read-only tools · 10
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age143 days
Maintainers1

Observed 2026-10-16 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · sendblue-browser-mcp@0.2.3 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads114Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed13Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Sendblue Browser MCP works

What sendblue-browser-mcp does

The sendblue-browser-mcp MCP server gives an MCP-compatible agent access to a separately running Chromium daemon. The daemon exposes an authenticated HTTP API, while the MCP package translates browser operations into agent-callable tools. This separates browser lifetime from an individual Claude, Cursor, Codex, or other agent session.

Browser state is organized into named sessions. Persistent sessions retain profile data across restarts, allowing a client to reuse cookies and an existing login. Sessions can also be isolated for concurrent work, reducing the chance that one agent changes another agent's browser state. A purge operation removes cookies and active-origin storage while preserving the session name.

How it works

The underlying process runs Chromium patched through Patchright. It can operate headlessly or with a configured display mode, and it supports options such as viewport size, user agent, locale, timezone, proxy, and Playwright tracing. Navigation can optionally produce screenshots according to the daemon's screenshot policy.

Requests are authorized with a bearer token, except for the health endpoint. The MCP wrapper needs the daemon URL and the same API key used by the daemon. Browser actions can also be performed directly with curl or through libraries that use the HTTP API.

For non-persistent sessions, the daemon can return a shared CDP URL. A separate Playwright, Puppeteer, undetected-chromedriver, or custom CDP client can then attach to the browser. Persistent sessions do not provide this shared CDP URL.

Setup and configuration

Install the daemon locally with Bun and Node.js available, install the Patchright Chromium binary, set BROWSER_USE_API_KEY, and start the development process. The repository also provides a Docker Compose path; its default data directory is ./data, and the service is exposed on 127.0.0.1:8787.

Configure the sendblue-browser-mcp MCP server with a command such as npx -y sendblue-browser-mcp@0.2.3. Set BROWSER_USE_URL to the daemon address and BROWSER_USE_API_KEY to the matching token. CDP remains loopback-only in the Docker setup unless its bind address and port mapping are explicitly changed.

Tools and capabilities

The MCP layer wraps the HTTP API with tools covering:

  • Health checks and session listing.
  • Session creation with persistence, headless mode, viewport, locale, timezone, proxy, user-agent, and trace settings.
  • Session inspection, deletion, and state purging.
  • URL navigation with wait and timeout options.
  • Full-page or selector-based PNG screenshots.
  • JavaScript execution in the page context through Playwright's evaluation API.
  • Cookie reading and writing.
  • Retrieval of buffered browser console messages.
  • CDP URL retrieval for eligible non-persistent sessions.

Scripts have a 30-second default timeout, can specify a longer timeout up to 120 seconds, or can disable the request timeout with zero. The script payload is limited to 200 kB. API errors use structured status codes and error objects, while detailed browser-side failures are logged by the daemon.

The sendblue-browser-mcp MCP server fits browser QA, authenticated workflow debugging, screenshot capture, and agent tasks that need an existing login. It is not described as a solution for hostile scraping at scale.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Sendblue Browser MCP

sendblue-browser-mcp is an MCP server that connects AI agents to a standalone stealth-patched Chromium daemon over HTTP. Its main tools cover health checks, named sessions, navigation, screenshots, JavaScript evaluation, cookies, console messages, session purging, and CDP URL retrieval for eligible sessions.

Install it in an MCP client with `npx -y sendblue-browser-mcp@0.2.3`, then set `BROWSER_USE_URL` and `BROWSER_USE_API_KEY`. The Chromium daemon must be running separately, either from the local Bun setup or with Docker Compose.

Yes, sendblue-browser-mcp works with Cursor through its MCP configuration. Add the server command and provide the daemon URL and bearer token in the environment section of Cursor's MCP configuration file.

Yes, persistent named sessions retain profile data across restarts. Create a persistent session, complete the login once, and later requests can use the retained cookies; purging clears browser state without removing the session identifier.

Yes, but CDP attachment is available for non-persistent sessions only. Retrieve the session's CDP URL from the API and use it with a compatible Playwright, Puppeteer, undetected-chromedriver, or other CDP client.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSendblue Browser MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sendblue-browser-mcp?style=directory)](https://allmcps.com/mcp/sendblue-browser-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/sendblue-browser-mcp"><img src="https://allmcps.com/api/badge/sendblue-browser-mcp?style=directory" alt="Sendblue Browser MCP on AllMCPs" /></a>