browsermcp
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., "@browsermcp go to https://www.google.com and search for 'browser automation'"
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.
Browser MCP
This is a fork of @browsermcp/mcp that fixes some reliability issues.
Installation
Add this to the mcp.json file
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": ["@conradkoh/browsermcp@latest"]
}
}
}Related MCP server: browseros-mcp
Finding Logs
The Browser MCP server logs its activity to a temporary file. When the server exits or crashes, the full path to this log file will be printed to stderr.
To find and view the logs:
Look for a message on
stderr(your terminal output) like:Exiting. Full logs available at: /var/folders/.../browsermcp-YYYY-MM-DDTHH-MM-SS-PID.logorFATAL ERROR: ... Full logs available at: /var/folders/.../browsermcp-YYYY-MM-DDTHH-MM-SS-PID.logTo view the most recent logs in real-time, you can use the following command (this might take a few seconds):
tail -f $(find /var/folders /tmp -name "browsermcp-*.log" 2>/dev/null -print0 | xargs -0 ls -t | head -n 1)(The
2>/dev/nulldirectly on thefindcommand will suppress "Permission denied" and other errors fromfinditself.)To view the entire content of the most recent log file:
cat $(find /var/folders /tmp -name "browsermcp-*.log" 2>/dev/null -print0 | xargs -0 ls -t | head -n 1)
Improvements
Improved logging: Logs are now more reliably written to a temporary directory.
Enhanced exit code handling: Implemented a finite state machine for better management of exit codes.
(WIP) Browser Gateway for multi-instance stability: A browser gateway has been added to resolve conflicts when multiple MCP servers connect to the browser, preventing crashes that previously required server restarts.
Available Tools
12 toolsbrowser_clickB
Perform click on a web page
Inputs: element (required), ref (required).
browser_get_console_logsA
Get the console logs from the browser
Inputs: no named parameters.
browser_go_backA
Go back to the previous page
Inputs: no named parameters.
browser_go_forwardA
Go forward to the next page
Inputs: no named parameters.
browser_hoverC
Hover over element on page
Inputs: element (required), ref (required).
browser_press_keyB
Press a key on the keyboard
Inputs: key (required).
browser_screenshotC
Take a screenshot of the current page
Inputs: no named parameters.
browser_select_optionB
Select an option in a dropdown
Inputs: element (required), ref (required), values (required).
browser_snapshotA
Capture accessibility snapshot of the current page. Use this for getting references to elements to interact with.
Inputs: no named parameters.
browser_typeB
Type text into editable element
Inputs: element (required), ref (required), text (required), submit.
browser_waitB
Wait for a specified time in seconds
Inputs: time (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool has a distinct action (click, hover, type, navigate, etc.) with no overlap. Even similar actions like go_back and go_forward are clearly differentiated by direction.
All tools follow a consistent `browser_<verb>` pattern in snake_case. The verbs are intuitive and match the action (e.g., browser_navigate, browser_type).
12 tools is appropriate for browser automation, covering navigation, interaction, screenshots, and debugging without being overwhelming or sparse.
The set covers core browsing interactions and debugging. Missing a refresh or scroll action, but most essential workflows are possible.
Related MCP Connectors
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Browserless MCP — wraps the Browserless headless-Chromium REST API (browserless.io)
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
MCP server to assist with JxBrowser development.
Related MCP Servers
- AlicenseAqualityCmaintenanceMulti-agent local browser automation MCP server with per-agent WebSocket paths, configurable ports, and fixes for upstream issues like port collisions and recursion bugs.231Apache 2.0
- AlicenseNot gradedqualityDmaintenanceStandalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.9 npmMIT

sendblue-browserofficial
AlicenseNot gradedqualityDmaintenanceMCP server that wraps sendblue-browser-use's HTTP API, providing tools to control a stealth-patched Chromium browser with persistent sessions, navigation, screenshots, and script execution.3MIT- AlicenseNot gradedqualityAmaintenanceThis server enables MCP clients and AI agents to perform browser automation with Playwright-compatible tools, persistent profiles, extensions, proxy support, and humanized interactions. It can be run via npm or Docker over stdio or Streamable HTTP for web research, automation, testing, and regional QA.431 npmMIT