home / mcp / hyper mcp browser server

Hyper MCP Browser Server

Provides automated browser-based page summaries and search across Google and Bing via an MCP server that launches a local browser or connects to a remote debugging port.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "bigsweetpotatostudio-hyper-mcp-browser": {
      "command": "npx",
      "args": [
        "-y",
        "hyper-mcp-browser"
      ],
      "env": {
        "CHROME_PATH": "undefined",
        "userDataDir": "undefined",
        "Hyper_browserURL": "http://localhost:9222",
        "Hyper_startingUrl": "https://github.com/BigSweetPotatoStudio/HyperChat",
        "Hyper_SEARCH_ENGINE": "google",
        "Hyper_isAutoLauncher": "true"
      }
    }
  }
}

You can run hyper-mcp-browser as an MCP server to automate browser-based tasks like page summaries and search across Google and Bing. This MCP enables you to launch a local browser instance from your workflow, control search behavior, and define the starting page you want to inspect or summarize.

How to use

You interact with this MCP server by starting it in stdio mode and then connecting an MCP client to it. The server launches a local browser (via a remote debugging port) and performs its tasks based on the configured environment variables. Set the starting URL, choose a search engine, and decide whether to auto-launch the local browser or use a remote debugging port.

How to install

Prerequisites: Node.js and npm installed on your system.

# Install and start the MCP server using npx
npx -y hyper-mcp-browser
```

```
# Optional: customize environment variables (example values shown)
export Hyper_browserURL=http://localhost:9222
export Hyper_isAutoLauncher=true
export Hyper_SEARCH_ENGINE=google
export Hyper_startingUrl=https://github.com/BigSweetPotatoStudio/HyperChat
export CHROME_PATH=undefined
export userDataDir=undefined
```

```
# Run with your environment settings (inline example)
Hyper_browserURL=http://localhost:9222 Hyper_isAutoLauncher=true Hyper_SEARCH_ENGINE=google Hyper_startingUrl=https://github.com/BigSweetPotatoStudio/HyperChat HyperCHROME_PATH=undefined Hyper_userDataDir=undefined npx -y hyper-mcp-browser

Configuration and usage notes

The MCP server relies on a remote browser debugging port and can be influenced by several environment variables. You can customize the default starting page, the search engine, and how the browser is launched. If you already have a browser with a remote debugging port open, you can connect to it via Hyper_browserURL instead of auto-launching locally.

Example start configuration

{
  "type": "stdio",
  "name": "hyper_mcp_browser",
  "command": "npx",
  "args": ["-y", "hyper-mcp-browser"],
  "env": [
    {"name": "Hyper_browserURL", "value": "http://localhost:9222"},
    {"name": "Hyper_isAutoLauncher", "value": "true"},
    {"name": "Hyper_SEARCH_ENGINE", "value": "google"},
    {"name": "Hyper_startingUrl", "value": "https://github.com/BigSweetPotatoStudio/HyperChat"},
    {"name": "CHROME_PATH", "value": "undefined"},
    {"name": "userDataDir", "value": "undefined"}
  ]
}

Troubleshooting

If the browser fails to launch or the remote debugging port is not accessible, verify that the port (default 9222) is open and that no other process is using it. Ensure that Node.js and npm are up to date, and confirm that the environment variables are correctly set before starting the MCP server.

Security considerations

When enabling remote debugging or auto-launching a local browser, be mindful of potential exposure of debugging interfaces. Use a localhost URL and secure access where possible, and avoid exposing debugging ports to untrusted networks.

Available tools

summarize_page

Summarizes content from the current page loaded in the browser, providing a concise overview.

search_engine

Performs web searches using the configured search engine (Google or Bing) and returns results.