Behead Browser MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Behead Browser MCPOpen https://example.com and take a screenshot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Behead Browser MCP
Browser automation and DevTools MCP servers backed exclusively by Behead Browser and Patchright Chromium.
behead-browser-mcphandles navigation, interaction, evaluation, screenshots, cookies, and request history.behead-browser-devtools-mcpadds multi-page control, UID snapshots, console and network inspection, CSS, emulation, traces, heap snapshots, and raw CDP.
Neither server launches Playwright, Puppeteer, Google Chrome, or the ordinary Chrome DevTools MCP.
Requirements
Node.js 20 or newer
A built Behead Browser checkout
Patchright's full Chromium installation
git clone https://github.com/Vuln-Inc/behead-browser.git
cd behead-browser
bun install --frozen-lockfile
bun run build
bunx patchright install chromiumRelated MCP server: Browser CDP MCP Server
Install
npm install -g github:Vuln-Inc/behead-browser-mcp
export BEHEAD_BROWSER_MODULE=/absolute/path/to/behead-browser/dist/index.jsThe environment variable must point to the compiled module exporting launchBeheadBrowser.
OpenCode
{
"mcp": {
"behead-browser": {
"type": "local",
"command": ["behead-browser-mcp"],
"environment": {
"BEHEAD_BROWSER_MODULE": "/absolute/path/to/behead-browser/dist/index.js"
}
},
"behead-devtools": {
"type": "local",
"command": ["behead-browser-devtools-mcp"],
"environment": {
"BEHEAD_BROWSER_MODULE": "/absolute/path/to/behead-browser/dist/index.js"
}
}
}
}Use behead_browser_* for normal automation and behead_devtools_* when console, network, performance, memory, or arbitrary CDP access is required.
Network history calls default to 50 records per page; use pageIdx and pageSize when more detail is needed.
Verify
npm test
BEHEAD_BROWSER_MODULE=/absolute/path/to/behead-browser/dist/index.js npm run test:integrationThe integration suite launches the real browser and verifies navigation, CDP evaluation, snapshots, console and network capture, performance metrics, tracing, and heap snapshots.
Limits
Behead Browser intentionally blocks service and shared workers. The DevTools server enables CDP Runtime in its own browser process, so use the automation server when minimizing debugger-observable behavior matters. Raw CDP access is powerful and should only be exposed to trusted MCP clients.
This server cannot be deployed
Maintenance
Related MCP Connectors
Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
- TabfleetOAuthcom.tabfleet
Launch, inspect, control, and share isolated cloud browsers for your agents.
Undetectable cloud browser sessions for AI agents and scrapers. Navigate, extract, click, captcha.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser through DevTools for automated testing, performance analysis, debugging, and web scraping. Provides reliable browser automation using Puppeteer with comprehensive DevTools access.1,440,876 npm3Apache 2.0
- FlicenseDqualityDmaintenanceProvides direct access to Chrome DevTools Protocol for browser automation, enabling navigation, screenshot capture, and execution of any CDP command for flexible browser control.42-
- AlicenseNot gradedqualityDmaintenanceProvides browser automation and DevTools capabilities via Puppeteer, with Docker support for consistent environments.1,477 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides browser automation and system-level control with multi-account isolation, session management, rich CDP operations, and YAML/JSON dual format support.0MIT