Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenGive an MCP-compatible AI assistant a local Chrome browser that it can open, navigate, read, and control.
Under maintenance: This project is still changing. The
mainbranch may be newer than the package published on npm. The npm badge above shows the published version used by@latest.
This package runs as a local Model Context Protocol (MCP) server. Your MCP client starts the server, and the server starts one Chrome process for browser automation.
Main features:
rebrowser-puppeteer-core and a small set of anti-detection settingsNo browser automation is invisible. Websites may still detect it or block it.
Please read this before using the server:
solve_captcha is currently a placeholder. It does not use a CAPTCHA-solving
service. Browser startup only makes a best-effort click on detected Turnstile
widgets.save_content_as_markdown is listed by the server, but the current workflow
validator blocks it. This is a known code issue.npx (included with the normal Node.js installer)stdio serverClaude Desktop is available on macOS and Windows. Other MCP clients can use this server on Linux.
You do not need to install this package globally. npx can download and run
the published package when your MCP client needs it.
The -y option prevents an npm install question from blocking the MCP server
while it starts.
mcpServers:{
"mcpServers": {
"puppeteer-real-browser": {
"command": "npx",
"args": [
"-y",
"puppeteer-real-browser-mcp-server@latest"
]
}
}
}
Claude Desktop stores this file here:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonSee the official local MCP server guide for the current Claude Desktop steps.
Run:
claude mcp add --transport stdio puppeteer-real-browser \
-- npx -y puppeteer-real-browser-mcp-server@latest
Then check the connection:
claude mcp get puppeteer-real-browser
Inside Claude Code, /mcp also shows server status.
The default scope is local to the current project. Add --scope user before
the server name if you want the server in all your projects. See the official
Claude Code MCP guide for scope details.
Create .cursor/mcp.json in one project, or ~/.cursor/mcp.json for all
projects:
{
"mcpServers": {
"puppeteer-real-browser": {
"command": "npx",
"args": [
"-y",
"puppeteer-real-browser-mcp-server@latest"
]
}
}
}
Restart Cursor after saving the file. See the official Cursor MCP guide for current configuration locations and formats.
Use a local stdio server with this command and argument list:
command: npx
args: -y puppeteer-real-browser-mcp-server@latest
The server communicates through standard input and standard output. Your MCP client must keep the process open while it uses the tools.
Ask your AI assistant:
Start the browser, open https://example.com, read the page text, and then close the browser.
The expected tool order is:
browser_init → navigate → get_content → browser_close
The server exposes 11 tools.
The server blocks blind interaction. Use this order:
browser_init → navigate → get_content → find_selector → click or type
After a new navigation, call get_content again before clicking or typing.
You can call wait after navigation when a page loads content slowly.
Browser options are inputs to browser_init. They are not top-level MCP
server settings.
contentPriority is an object with prioritizeContent and
autoSuggestGetContent Boolean values. It changes suggestions, but it does not
remove the required content-first workflow.
Example request:
{
"headless": true,
"proxy": "http://proxy.example.com:8080",
"connectOption": {
"timeout": 60000,
"slowMo": 100
},
"customConfig": {
"chromePath": "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
}
}
The server first checks these environment variables:
CHROME_PATHPUPPETEER_EXECUTABLE_PATHIf neither points to a file, the server checks common Chrome and Chromium locations. On Windows, it also checks the registry and common portable paths.
You can set CHROME_PATH in the MCP client configuration:
{
"mcpServers": {
"puppeteer-real-browser": {
"command": "npx",
"args": [
"-y",
"puppeteer-real-browser-mcp-server@latest"
],
"env": {
"CHROME_PATH": "/absolute/path/to/chrome"
}
}
}
}
PROXY_URL is not a supported environment variable. Pass a proxy to
browser_init instead.
The server keeps the exact launcher handle and process ID for the Chrome process it starts. Normal close, startup failure, timeout, MCP disconnect, and signal shutdown all clean up through that handle. It does not search for or close Chrome by process name.
For safety, the server rejects settings that could attach to another browser or take ownership of a personal Chrome profile:
customConfig.userDataDircustomConfig.portcustomConfig.portStrictModecustomConfig.handleSIGINTconnectOption.browserURLconnectOption.browserWSEndpointconnectOption.transport--remote-debugging-port, --remote-debugging-pipe, and --user-data-dir
inside custom Chrome flagsUse profilePath for persistent automation data. The directory must be
absolute and either empty or already marked as owned by this server.
Check the tools are installed:
node --version
npm --version
npx --version
Check that Node.js is version 18 or newer.
Check the JSON file for missing commas or quotes.
Fully quit and reopen the MCP client.
If a desktop app cannot find npx, use its absolute path as command.
Run which npx on macOS/Linux or where npx on Windows to find it.
Claude Desktop logs are stored here:
~/Library/Logs/Claude%APPDATA%\Claude\logsFind the real Chrome executable, then set CHROME_PATH in the MCP client
configuration. Common examples are:
C:/Program Files/Google/Chrome/Application/chrome.exe/Applications/Google Chrome.app/Contents/MacOS/Google Chrome/usr/bin/google-chrome or /usr/bin/chromiumDo not run the MCP client as Administrator or use sudo npm install -g only to
solve a Chrome path problem.
This can be normal. A stdio MCP server waits for protocol messages from an MCP
client. Use the MCP Inspector instead of typing into the process.
Test the published package:
npx -y @modelcontextprotocol/inspector \
npx puppeteer-real-browser-mcp-server@latest
See the official MCP Inspector guide for usage details.
Follow the required workflow:
browser_initnavigateget_contentfind_selector when you need a selectorclick or typeIf the page changed, call get_content again.
browser_close, then start it again.connectOption.timeout in the browser_init input.Search or open a GitHub issue. Include:
Do not include passwords, cookies, tokens, or private page content.
git clone https://github.com/withLinda/puppeteer-real-browser-mcp-server.git
cd puppeteer-real-browser-mcp-server
npm ci
npm run build
Test the local build with the MCP Inspector:
npx -y @modelcontextprotocol/inspector node dist/index.js
To use the local build in an MCP client, use an absolute path:
{
"mcpServers": {
"puppeteer-real-browser-local": {
"command": "node",
"args": [
"/absolute/path/to/puppeteer-real-browser-mcp-server/dist/index.js"
]
}
}
}
src/index.ts MCP stdio server and request handlers
src/tool-definitions.ts Tool names and input schemas
src/browser-manager.ts Browser state, detection, and configuration
src/managed-browser-session.ts Owned Chrome launch and cleanup
src/handlers/ Tool implementations
src/*.test.ts Unit and regression tests
test/integration/ MCP protocol integration tests
test/e2e/ Real-browser tests
test/safety/ Browser cleanup safety guard
scripts/check-packaged-server.ts Package smoke test
Use TDD for behavior changes: write one failing test, make it pass, then clean up the code.
# Browser cleanup safety guard
npm run test:safety
# Fast source tests
npm run test:unit
# MCP protocol integration tests
npm run test:integration
# Build the package
npm run build
# Test the built npm package shape and stdio lifecycle
npm run test:package:smoke:built
# Real Chrome tests
npm run test:e2e
# Release-focused automated checks
npm run test:all
During TDD, use npm run test:watch. Before running real-browser tests, note
the Chrome processes already open on your machine. After testing, verify that
only the Chrome process started by the test was closed.
Issues and pull requests are welcome. For a code change:
This project uses the MIT License.
The original implementation and public API were based on
puppeteer-real-browser
by ZFC Digital. The current source replaces that end-of-life runtime dependency
with an internal managed launcher built from chrome-launcher,
rebrowser-puppeteer-core, and ghost-cursor.
Provides AI assistants with powerful, detection-resistant browser automation capabilities built on ZFC Digital's puppeteer-real-browser package.
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Puppeteer Real Browser läuft lokal über stdio.
Zuletzt geprüft: 2026-10-28. Provides AI assistants with powerful, detection-resistant browser automation capabilities built on ZFC Digital's puppeteer-real-browser package.