Skip to main content
Glama
browsermcp
by conradkoh

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:

  1. Look for a message on stderr (your terminal output) like: Exiting. Full logs available at: /var/folders/.../browsermcp-YYYY-MM-DDTHH-MM-SS-PID.log or FATAL ERROR: ... Full logs available at: /var/folders/.../browsermcp-YYYY-MM-DDTHH-MM-SS-PID.log

  2. To 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/null directly on the find command will suppress "Permission denied" and other errors from find itself.)

  3. 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

  1. Improved logging: Logs are now more reliably written to a temporary directory.

  2. Enhanced exit code handling: Implemented a finite state machine for better management of exit codes.

  3. (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 tools
browser_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_navigateB

Navigate to a URL

Inputs: url (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

    A3.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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).

    Tool Count5/5

    12 tools is appropriate for browser automation, covering navigation, interaction, screenshots, and debugging without being overwhelming or sparse.

    Completeness4/5

    The set covers core browsing interactions and debugging. Missing a refresh or scroll action, but most essential workflows are possible.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Multi-agent local browser automation MCP server with per-agent WebSocket paths, configurable ports, and fixes for upstream issues like port collisions and recursion bugs.
      23
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Standalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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.
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This 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 npm
      MIT