# Hyperbrowser

> Hosted Chromium with proxies and anti-bot evasion for AI agents.

[Canonical HTML page](https://top-mcps.com/mcp/hyperbrowser) · [server.json](https://top-mcps.com/mcp/hyperbrowser.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "hyperbrowser": {
      "command": "npx",
      "args": [
        "-y",
        "hyperbrowser-mcp"
      ],
      "env": {
        "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export HYPERBROWSER_API_KEY=your-hyperbrowser-api-key
claude mcp add hyperbrowser -- npx -y hyperbrowser-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "hyperbrowser": {
      "command": "npx",
      "args": [
        "-y",
        "hyperbrowser-mcp"
      ],
      "env": {
        "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "hyperbrowser": {
      "command": "npx",
      "args": [
        "-y",
        "hyperbrowser-mcp"
      ],
      "env": {
        "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "hyperbrowser": {
      "command": "npx",
      "args": [
        "-y",
        "hyperbrowser-mcp"
      ],
      "env": {
        "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "hyperbrowser": {
      "command": "npx",
      "args": [
        "-y",
        "hyperbrowser-mcp"
      ],
      "env": {
        "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "hyperbrowser-mcp"
          ],
          "env": {
            "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.hyperbrowser]
command = "npx"
args = [
  "-y",
  "hyperbrowser-mcp",
]
env = { HYPERBROWSER_API_KEY = "${HYPERBROWSER_API_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "hyperbrowser": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "hyperbrowser-mcp"
        ]
      },
      "env": {
        "HYPERBROWSER_API_KEY": "${HYPERBROWSER_API_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Apps directory`

Hyperbrowser doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

```none

```

## At a glance

- **Maintainer:** Hyperbrowser
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** HYPERBROWSER_API_KEY
- **Supported clients:** Claude, Cursor, VS Code, Windsurf, Any MCP-compatible client, Hyperbrowser account
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-05-31
- **GitHub stars:** 764 (fetched 2026-06-02T11:55:52.455Z)
- **Score:** 69/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/hyperbrowserai/mcp

## Security & scope

- **Access scope:** network
- **Sandbox:** Hosted on Hyperbrowser infrastructure. Local MCP holds only an API key. Sessions are isolated per request; nothing persists between sessions unless you save state explicitly.
- **Gotchas:**
  - Session-minute billing — long-lived sessions cost real money.
  - Stored cookies / auth between sessions require explicit profile save; do not assume persistence.
  - Hosted infrastructure means traffic exits Hyperbrowser IPs — visible in destination-site logs.

## Quick answer

**What it does.** Spawns hosted Chromium sessions and exposes navigation, click, fill, screenshot, and structured page extraction. Returns a session URL for live debug.

**Best for:**
- Production agent browsing
- Sites with anti-bot defences
- Geographic IP routing
- Parallel browser sessions
- Captcha-protected pages

**Not for:**
- Workflows where local Playwright works fine
- Strictly data-residency-bound flows
- Cost-sensitive long-running sessions

## Description

The official Hyperbrowser MCP exposes hosted Chromium sessions designed for AI agents — each request gets a fresh isolated browser, with built-in residential proxies, captcha handling, and stealth-mode defaults. Built for the case where local Puppeteer / Playwright gets blocked.

## Why it matters

Local browser automation hits anti-bot defences fast on consumer sites. Hosted browsers with residential IPs and stealth defaults are the practical answer for production agent browsing.

## Key features

- Hosted Chromium per session
- Residential proxies (50+ countries)
- Captcha solving built in
- Stealth-mode defaults
- Live session URL for debugging

## FAQ

### How is it different from Browserbase?

Both hosted Chromium; Hyperbrowser leans harder on built-in captcha + stealth defaults. Browserbase has stronger DevTools integration. Pick by which problem hurts more.

### Pricing model?

Per session-minute + per proxy GB. Free tier covers prototyping; production loops need a paid plan.

### Live session URL — what is it for?

Debug. Open the URL in your own browser to watch what the agent is doing in real time. Invaluable when an automation goes off the rails.

### Captcha solving — how reliable?

Good on common challenges (reCAPTCHA v2/v3, Cloudflare). Site-specific defences (Datadome, PerimeterX) still block sometimes. Test against your target before committing.

## Changelog

- **2026-05-31** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-04-02** — Initial directory listing.