5 ms·
Show HN: Hyperbrowser MCP Server – Connect AI agents to the web through browsers
Hi HN! Excited to share our MCP Server at Hyperbrowser - something we’ve been working on for a few days. We think it’s a pretty neat way to connect LLMs and IDEs like Cursor / Windsurf to the internet.
Our MCP server exposes seven tools for data collection and browsing:
1. `scrape_webpage` - Extract formatted (markdown, screenshot etc) content from any webpage
2. `crawl_webpages` - Navigate through multiple linked pages and extract LLM-friendly formatted content
3. `extract_structured_data` - Convert messy HTML into structured JSON
4. `search_with_bing` - Query the web and get results with Bing search
5. `browser_use_agent` - Fast, lightweight browser automation with the Browser Use agent
6. `openai_computer_use_agent` - General-purpose automation using OpenAI’s CUA model
7. `claude_computer_use_agent` - Complex browser tasks using Claude computer use
You can connect the server to Cursor, Windsurf, Claude desktop, and any other MCP clients with this command `npx -y hyperbrowser-mcp` and a Hyperbrowser API key. We're running this on our cloud browser infrastructure that we've been developing for the past few months – it handles captchas, proxies, and stealth browsing automatically.
Some fun things you can do with it: (1) deep research with claude desktop, (2) summarizing the latest HN posts, (3) creating full applications from short gists in Cursor, (3) automating code review in cursor, (4) generating llms.txt for any website with windsurf, (5) ordering sushi from windsurf (admittedly, this is just for fun - probably not actually going to do this myself).
We're building this server in the open and would love feedback from anyone building agents or working with web automation. If you find bugs or have feature requests, please let us know! One big issue with MCPs in general is that the installation UX sucks and auth credentials have to be hardcoded. We don’t have a solution to this right now but Anthropic seems to be working on something here so excited for that to come out. Love to hear any other complaints / thoughts you have about the server itself, Hyperbrowser, or the installation experience.
You can check us out at https://hyperbrowser.ai https://hyperbrowser.ai or check out the source code at https://github.com/hyperbrowserai/mcp https://github.com/hyperbrowserai/mcp
- pizzafeelsright 2y agoFantastic. MCPs are showing promise.
- fosterfriends 2y ago++ love that folks are trying to build companies on MCP. Good luck!
- shrisukhani 2y agoThanks! :)
- shrisukhani 2y agoThanks! And yeah MCP is super promising. We announced this on X and LinkedIn yesterday and the response has been really good. A lot of people with a bunch of use cases. One surprising thing is there’s also a bunch of semi/non-technical people using our MCP server and the installation experience for them rn just absolutely sucks. I think once auth and 1-click install are solved, MCP could become the standard way to integrate tools with LLMs
- _pdp_ 2y agoThe MCP protocol is really not that good. The stateful nature of it makes it only suitable as a local desktop RPC pipe - certainly not something that will work well on mobile nor anything anyone would like to try to run maintain in a server-to-serve context. It is fine if that is the scope. It is also understandable why Anthropic chose to use a stateful protocol where stateless HTTP would be more than enough. They are catering for the default transport layer which is stdio based where state needs to be established. There are also other aspects of it that are simply unnecessarily complex and resource intensive for no good reasons.
- pkkkzip 2y agowhat do you suggest instead of MCP ?
- _pdp_ 2y agoWell OpenAPI. You don't need some wired debugging tools nobody knows how to use, a stateful protocol that is hard to troubleshoot, etc. There is plenty of support already built into standard HTTP services and Swagger - abundance of tools and documentation too and what we call function calling is basically JSON Schema which is at the core of swagger definitions. MCP is trying to reinvent OpenAPI but in the wrong way.
- TheTaytay 2y agoThis looks cool. 1) I looked at the pricing. Is search included in the price - (you just pay credits/browser time?) 2) Can you tell me more about the source of your residential proxies? I am new to this space, so don’t know how people source these legitimately. Thanks!
- shrisukhani 2y agoThanks! 1) Yep, you just pay from browser time and proxy usage 2) We use a handful of proxy providers under the hood ourselves. There’s a lot of shady ones but we only work with ones where we’ve vetted the source of. Different providers source proxies in different ways - directly from ISPs, paying end sources for proxies etc
- deleted 2y ago[deleted]
- ranger_danger 2y agoWhat is your vetting process and who have you vetted?
- xena 2y agoIs there support for robots.txt so service operators can opt out of your mass scraping?
- soulofmischief 2y agoWould you like to explain how directing your user agent to use the internet just as you would in order to complete a task or solve a problem is "mass scraping"?
- ranger_danger 2y agoIntent.
- soulofmischief 2y agoCare to elaborate? That is not a substantial argument.
- dkh 2y ago> to use the internet just as you would Your premise is flawed, or at the very least, far from guaranteed. One could use tools like this to use to browse the internet only as they would otherwise. One could also use it for mass scraping, and many do. If you've looked at HN on previous days this week, there's been a front-page story nearly every day about problems resulting from exactly that. The parent comment was perhaps a bit too snarky with the assumption that this could/would only be used for malicious behavior on a large scale, but your assumption that it wouldn't be is not any better, and also runs contrary to what people have been experiencing and discussing in this arena in recent days
- shrisukhani 2y agoNo, we don't enforce any robots.txt restrictions ourselves. We also don't do any scraping ourselves. We provide browser infrastructure that operates like any normal browser would - what users choose to do with it is up to them. We're building tools that give AI agents the same web access capabilities that humans have, don't think it's our place to impose any additional limitations.
- dennisaxu 2y agodope