Alternatives
Products that do what Webmcp-react – React hooks that turn your website into an MCP server does
Chrome recently shipped navigator.modelContext in Early Preview. It's a browser API that lets any website expose typed, callable tools to AI agents. I built webmcp-react because we wanted a simple way to add tools to our React app and figured others could benefit from it as well. You wrap your app in , call useMcpTool with a Zod schema, and that's it. Handles StrictMode, SSR, dynamic mount/unmount, and all of the React lifecycle. It also comes with a Chrome extension in the repo that acts as a bridge for MCP clients (Claude Code, Cursor, etc.), since they can't access…
- 1
- 2
- 3BM
2025 · browsermcp.io
- 4
- 5CA
Hey HN, we built a Chrome Extension (https://www.magicpatterns.com/extension) that converts a snippet of any website to an isolated React component. Demo video: https://youtu.be/hutUYDkyE_A How it works: 1) Iterate through each node in the selected DOM tree, 2) For each element, find any matching CSS selectors / inline styles, 3) Use window.getComputedStyle to get the deterministic values, 4) Construct JSX It was pretty hard producing the minimal code necessary while maintaining the same visual look. To do this, we implemented things like abstracting out…
2024 · chromewebstore.google.com
- 6AV
I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head, and then jump between the browser and IDE to test. I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient. Hope it’s useful!
2022 · dev.aspect.app
- 7
- 8
- 9
- 10
- 11
- 12
Let AI create a full-stack web app based on your description
2023
- 13IM
Hi! I made a React compatibility library for a Virtual DOM library (https://github.com/aidenybai/million). The idea is to have much faster rendering (a compiler optimizes virtual DOM beforehand) while ensuring the same developer experience React provides. This is very, VERY early stage, so be prepared for weird bugs / plugin incompatibility / etc. If you have any suggestions, I'd be more than happy if you replied in a comment with it! You can spin up the demo here >> https://stackblitz.com/github/aidenybai/million-react-compat
2022
- 14
- 15WB
Hi HN, I built webctl because I was frustrated by the gap between curl and full browser automation frameworks like Playwright. I initially built this to solve a personal headache: I wanted an AI agent to handle project management tasks on my company’s intranet. I needed it to persist cookies across sessions (to handle SSO) and then scrape a Kanban board. Existing AI browser tools (like current MCP implementations) often force unsolicited data into the context window—dumping the full accessibility tree, console logs, and network errors whether you asked for them or not. webctl is an attempt…
Jan 2026 · github.com
- 16
- 17OS
Hi HN, I forked chromium and built agent-browser-protocol (ABP) after noticing that most browser-agent failures aren’t really about the model misunderstanding the page. Instead, the problem is that the model is reasoning from a stale state. ABP is designed to keep the acting agent synchronized with the browser at every step. After each action (click, type, etc), it freezes JavaScript execution and rendering, then captures the resulting state. It also compiles the notable events that occurred during that action loop, such as navigation, file pickers, permission prompts, alerts, and downloads,…
Mar 2026 · github.com
- 18WP
Hey HN, we just shipped a browser with an inbuilt MCP server! We're a YC startup (S24) building BrowserOS — an open‑source Chromium fork. We're a privacy‑first alternative to the new wave of AI browsers like Dia, Perplexity Comet. Since launching ~3 months ago, the #1 request has been to expose our browser as an MCP server. -- Google beat us to launch with chrome-devtools-mcp (solid product btw), which lets you build/debug web apps by connecting Chrome to coding assistants. But we wanted to take this a step further: we packaged the MCP server directly into our browser binary. That gives…
Oct 2025 · github.com
- 19
- 20AJ
I've been building a web UI library for a side project of mine. I thought it might be useful to others, so I'm releasing it as open source. To put it simply, I realized that most of my pain points with React come from its declarative model ui=f(state). So I'm trying something that I'm calling "imperative JSX." Instead of treating JSX as the source of truth for your UI, it essentially becomes a query interface for DOM manipulation. I first had the idea for it a few months ago, and only began writing it in earnest last week, so it's extremely early and nowhere near production-ready. Still, I'd…
2024 · npmjs.com
- 21TO
Apr 2026 · thales.me
- 22HM
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…
2025 · github.com
- 23WD
Hi HN, recently there have been a lot of discussions about Chrome's dominance on the Web leading to many websites being broken for alternative browsers. I think one of the reasons for this is that browser automation is hard and manual testing is often limited to the browser developers themselves use. I've distilled my best practices for browser test automation into the following project and hope it helps other developers to test their projects with more browsers: https://github.com/blueimp/wdio It's a Docker setup for WebdriverIO with automatic screenshots, image diffing…
2019
- 24OS
Large Language Models (LLMs) are powerful, but they’re limited by fixed context windows and outdated knowledge. What if your AI could access live search, structured data extraction, OCR, and more—all through a standardized interface? We built the JigsawStack MCP Server, an open-source implementation of the Model Context Protocol (MCP) that lets any AI model call external tools effortlessly. Here’s what it unlocks: - Web Search & Scraping: Fetch live information and extract structured data from web pages. - OCR & Structured Data Extraction: Process images, receipts, invoices, and handwritten…
2025
Ranked by how close each launch is in meaning, then by votes. Refine with a description →