Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"browser-mcp-server": {
"args": [
"-y",
"browser-mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
No description provided.
This server is thin — proceed with caution. Help improve this page →
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'browser-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked browser-mcp-server against OSV.dev.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser / developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
40+ production-ready SwiftUI recipes for building full-stack iOS apps via MCP.
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
MCP Security Weekly
Get CVE alerts and security updates for Browser Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Browser automation and web scraping MCP server powered by headless Chromium.
Standalone binary that exposes 27 browser automation and web scraping tools over MCP (Model Context Protocol) via stdio or HTTP transport using JSON-RPC 2.0.
--transport flagSingle crate, seven source modules:
| Module | Responsibility |
|---|---|
src/main.rs | CLI parsing (clap), entry point, transport selection, tool definitions, tool dispatch |
src/mcp.rs | JSON-RPC 2.0 types, MCP tool result helpers, async stdio loop, async dispatch |
src/http.rs | HTTP transport: axum server, Bearer auth, MCP HTTP session management |
src/browser.rs | Chromium lifecycle, stealth patches, 20 browser tool handlers, session cleanup |
src/search.rs | url_read, url_read_raw, url_search (Brave/DDG) |
src/content.rs | read_markdown (Readability), probe, submit_form |
src/fetch.rs | fetch (HTTP-first, browser fallback) |
browser-mcp-server [OPTIONS]
Options:
--transport <MODE> Transport mode: stdio or http [default: stdio]
--host <HOST> Host to bind HTTP server [default: 127.0.0.1]
--port <PORT> Port for HTTP server [default: 8080]
--auth <TOKEN> Bearer token for HTTP authentication (optional)
--chrome-path <PATH> Path to Chrome/Chromium binary (auto-detected if not set)
--headless Run in headless mode [default: true]
--max-sessions <N> Max concurrent browser sessions [default: 5]
--session-timeout-secs <N> Session auto-close after inactivity [default: 300]
--page-load-timeout-ms <N> Per-navigation timeout [default: 60000]
--content-timeout-ms <N> Page content extraction timeout [default: 60000]
--max-content-bytes <N> Max HTML size before truncation [default: 1000000]
--no-sandbox Disable Chrome sandbox (required in Docker)
--data-dir <PATH> Data directory for screenshots & Chrome profile
--version Print version and exit
cargo build --release
nix develop # dev shell with all dependencies
nix build # build the package
--chrome-path| Crate | Purpose |
|---|---|
chromiumoxide | Headless Chrome/Chromium via CDP |
htmd | HTML to Markdown conversion |
readability | Mozilla Readability content extraction |
reqwest | HTTP client for lightweight tools |
futures | Stream handling for Chrome events |
url | URL parsing |
dirs | Default data directory |
clap | CLI argument parsing |
serde, serde_json | JSON serialization for MCP protocol |
tracing, tracing-subscriber | Structured logging to stderr |
axum | HTTP server framework for MCP HTTP transport |
tokio | Async runtime |
uuid | Session ID generation (UUID v4) |
The server supports two transport modes: