Connect Human Browser to your MCP-aware client

Human Browser ships a Model Context Protocol server that gives AI agents a hosted Chromium tab on a clean residential connection. The agent runs user-authorized tasks — research, monitoring, form-fill, public-data gathering — while the human watches a live viewer and can take over at any moment. Drop it into Claude Desktop, Cursor, or Cline with one config block.

Install

The MCP server is bundled inside the same npm package as the SDK. Two transports are supported: local stdio (recommended for Claude Desktop) and remote HTTP (recommended for Cursor and Cline, which support native HTTP transport).

npx -y @virixlabs/humanbrowser mcp

npm install -g @virixlabs/humanbrowser

https://agent.humanbrowser.cloud/mcp

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Local stdio works out of the box; for the hosted endpoint, wrap with mcp-remote until Claude Desktop ships native HTTP transport.

{
  "mcpServers": {
    "humanbrowser": {
      "command": "npx",
      "args": ["-y", "@virixlabs/humanbrowser", "mcp"],
      "env": { "HB_TOKEN": "hb_live_..." }
    }
  }
}

Cursor

Open Settings → Features → MCP Servers → Add new server. Cursor supports native HTTP transport.

{
  "mcpServers": {
    "humanbrowser": {
      "url": "https://agent.humanbrowser.cloud/mcp",
      "headers": { "Authorization": "Bearer hb_live_..." }
    }
  }
}

Cline (VS Code extension)

Open the Cline sidebar, click the MCP icon, then Configure MCP Servers. Cline supports both stdio and HTTP transports.

{
  "mcpServers": {
    "humanbrowser": {
      "url": "https://agent.humanbrowser.cloud/mcp",
      "headers": { "Authorization": "Bearer hb_live_..." }
    }
  }
}

Authentication

Human Browser uses a single bearer token, passed either as the HB_TOKEN environment variable (stdio transport) or the Authorization: Bearer … header (HTTP transport). Tokens look like hb_live_… and carry a prepaid balance — there are no per-key seat fees or quotas to manage.

To obtain one:

1. Visit humanbrowser.cloud and enter your email.
2. Receive your hb_live_… token by email and add a first top-up of $1 (enough for about 4 typical tasks — the median task takes about 8 agent steps and costs $0.24 all-in).
3. Top up later via Stripe or crypto when you want to keep going. Prepaid, no auto-renew.

The legacy variable name HUMANBROWSER_API_TOKEN is still accepted as an alias for HB_TOKEN.

Tools exposed

Each tool ships with MCP annotations (readOnlyHint, destructiveHint, openWorldHint) so MCP-aware clients can render the correct approval UI and so directory reviewers can assess scope at a glance.

Use cases — legitimate web access

Human Browser is designed for tasks a person could reasonably do themselves in a browser, executed by an agent on their behalf and supervised in real time.

Live viewer & human takeover

Every humanbrowser_run response includes a viewer_url — a real-time MJPEG stream of the Chromium tab the agent is driving. The human owner can:

Pricing

Measured on production over 132 successful customer tasks (Sep 2026), re-priced at today's rates: the median task took about 8 agent steps and costs $0.24 all-in, a quarter cost $0.12 or less. Browser time is billed per second; sessions under 30 seconds and time under human control are not billed.

Compliance & acceptable use

Human Browser is built to be reviewable by directory operators (Anthropic Connectors, Cline MCP Marketplace, OpenAI Apps) and safe for end users. Please read this carefully before deploying.

Full Terms of Service and Privacy Policy. Abuse reports: [email protected].