Hyperbrowser MCP Server

If you already use Hyperbrowser, the hyperbrowser mcp server is the piece that lets your assistant work with it directly. Hyperbrowser Model Context Protocol Server.

What the server does

This is Hyperbrowser's Model Context Protocol (MCP) Server. It provides various tools to scrape, extract structured data, and crawl webpages. It also provides easy access to general purpose browser agents like OpenAI's CUA, Anthropic's Claude Computer Use, and Browser Use.

Installation

hyperbrowser-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• scrape_webpage — Extract formatted (markdown, screenshot etc) content from any webpage
• crawl_webpages — Navigate through multiple linked pages and extract LLM-friendly formatted content
• extract_structured_data — Convert messy HTML into structured JSON
• search_with_bing — Query the web and get results with Bing search
• browser_use_agent — Fast, lightweight browser automation with the Browser Use agent
• openai_computer_use_agent — General-purpose automation using OpenAI’s CUA model
• claude_computer_use_agent — Complex browser tasks using Claude computer use
• create_profile — Creates a new persistent Hyperbrowser profile
• delete_profile — Deletes an existing persistent Hyperbrowser profile
• list_profiles — Lists existing persistent Hyperbrowser profiles
• Development — For development purposes, you can run the server directly from the source code

Credentials and setup notes

Configuration is passed through the environment: HYPERBROWSER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hyperbrowser.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Hyperbrowser's toolset — scrape_webpage, crawl_webpages, extract_structured_data and 8 more — is a fair guide to whether it matches your workflow. It is maintained by a_harmless_pyro; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.