MCP server
by hyperbrowserai
Hyperbrowser enables web scraping, internet scraping, and automation to scrape any website for data extraction or web cr
Connects to Hyperbrowser's API for web scraping, data extraction, and browser automation. Provides access to browser agents like OpenAI's CUA and Anthropic's Claude Computer Use.
Hyperbrowser is an official MCP server published by hyperbrowserai that provides AI assistants with tools and capabilities via the Model Context Protocol. Hyperbrowser enables web scraping, internet scraping, and automation to scrape any website for data extraction or web cr It is categorized under browser automation.
You can install Hyperbrowser in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Hyperbrowser is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Hyperbrowser is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Hyperbrowser is the kind of server we cite when onboarding engineers to host + tool permissions.
I recommend Hyperbrowser for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Hyperbrowser into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend Hyperbrowser for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Hyperbrowser reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired Hyperbrowser into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Hyperbrowser is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Hyperbrowser is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, Hyperbrowser benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 66
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.
More information about the Hyperbrowser can be found here. The hyperbrowser API supports a superset of features present in the mcp server.
More information about the Model Context Protocol can be found here.
To install the server, run:
npx hyperbrowser-mcp <YOUR-HYPERBROWSER-API-KEY>
Add to ~/.cursor/mcp.json like this:
{
"mcpServers": {
"hyperbrowser": {
"command": "npx",
"args": ["-y", "hyperbrowser-mcp"],
"env": {
"HYPERBROWSER_API_KEY": "YOUR-API-KEY"
}
}
}
}
Add to your ./codeium/windsurf/model_config.json like this:
{
"mcpServers": {
"hyperbrowser": {
"command": "npx",
"args": ["-y", "hyperbrowser-mcp"],
"env": {
"HYPERBROWSER_API_KEY": "YOUR-API-KEY"
}
}
}
}
For development purposes, you can run the server directly from the source code.
Clone the repository:
git clone git@github.com:hyperbrowserai/mcp.git hyperbrowser-mcp
cd hyperbrowser-mcp
Install dependencies:
npm install # or yarn install
npm run build
Run the server:
node dist/server.js
This is an example config for the Hyperbrowser MCP server for the Claude Desktop client.
{
"mcpServers": {
"hyperbrowser": {
"command": "npx",
"args": ["--yes", "hyperbrowser-mcp"],
"env": {
"HYPERBROWSER_API_KEY": "your-api-key"
}
}
}
}
scrape_webpage - Extract formatted (markdown, screenshot etc) content from any webpagecrawl_webpages - Navigate through multiple linked pages and extract LLM-friendly formatted contentextract_structured_data - Convert messy HTML into structured JSONsearch_with_bing - Query the web and get results with Bing searchbrowser_use_agent - Fast, lightweight browser automation with the Browser Use agentopenai_computer_use_agent - General-purpose automation using OpenAI’s CUA modelclaude_computer_use_agent - Complex browser tasks using Claude computer usecreate_profile - Creates a new persistent Hyperbrowser profile.delete_profile - Deletes an existing persistent Hyperbrowser profile.list_profiles - Lists existing persistent Hyperbrowser profiles.To install Hyperbrowser MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @hyperbrowserai/mcp --client claude
The server provides the documentation about hyperbrowser through the resources methods. Any client which can do discovery over resources has access to it.
This project is licensed under the MIT License.
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.