Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Clone any web page from a URL into a verified offline HTML copy, embed, or rebuild.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://webembedding-jongkos-mcp.vercel.app/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"web-embedding": {
"command": "npx",
"args": [
"-y",
"web-embedding",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http web-embedding https://webembedding-jongkos-mcp.vercel.app/mcpclaude mcp add web-embedding -- npx -y web-embedding mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"web-embedding": {
"url": "https://webembedding-jongkos-mcp.vercel.app/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"web-embedding": {
"command": "npx",
"args": [
"-y",
"web-embedding",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"web-embedding": {
"type": "http",
"url": "https://webembedding-jongkos-mcp.vercel.app/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"web-embedding": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"web-embedding",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://webembedding-jongkos-mcp.vercel.app/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account jongko54, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.3.12) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
webEmbedding clones any web page from its URL for AI coding agents. Give Claude Code, Codex, Cursor, or any MCP client a URL and it returns a verified clone: the original embed when the page allows it, otherwise a self-contained offline HTML snapshot (inlined CSS, shadow DOM, localized fonts and images) or a bounded rebuild, scored against desktop, tablet, and mobile screenshots of the live page.
Add it to your agent in one line:
claude mcp add web-embedding -- npx -y web-embedding@latest mcp # Claude Code
codex mcp add web-embedding -- npx -y web-embedding@latest mcp # Codex CLI
Then ask: *"Clone https://example.com into ./clone and tell me the fidelity score."* (Machine-readable summary for LLMs: llms.txt.)
webEmbedding is a source-first website cloning engine: it captures live pages with Playwright, replays network evidence from HAR artifacts, rebuilds only when direct reuse is blocked, and self-verifies the result.
It ships as a Skill + MCP server. Instead of asking a model to "clone this site" from a screenshot, it inspects the URL, chooses a reuse or rebuild route, captures DOM/runtime HTML/styles/assets/network traces, generates bounded frontend reconstruction artifacts, and checks the output with visual, DOM, computed-style, interaction, and responsive-breakpoint verification.
GitHub listing, social preview, and launch-copy recommendations are in docs/github-listing.md.
The current pipeline is strongest for static and semi-static web pages:
It is not a full backend or app-logic clone engine. Login-only screens, app-first or native-app-required services, captcha-heavy sites, maps, games, canvas/WebGL-heavy pages, real-time feeds, payments, booking flows, and private server behavior still need separate handling.
Operationally, the repo is now a production-candidate clone engine for URL-based capture and bounded reconstruction: jobs can be queued, network evidence can be replay-audited from HAR artifacts, authenticated dashboard runs can be driven from user-owned browser state, and local gates verify the route corpus, score checks, package contents, and CI wiring. The remaining hard boundary is server-side product behavior, not front-end evidence capture and reconstruction.
Local benchmark runs from this repo (scripts/check_clone_quality_bench.py, mobile + tablet breakpoints, 2026-10-28):
| URL | Path | Score | Wall time |
|---|---|---|---|
https://developer.mozilla.org/en-US/ | runtime snapshot | root 99, visual 100, mobile 99, tablet 99 | ~34 s |
https://lit.dev/ (web components / shadow DOM) | runtime snapshot | root 99, visual 100, mobile 98, tablet 98 | ~40 s |
https://www.mozilla.org/ | runtime snapshot | root 95, visual 100, mobile 95, tablet 95 | ~43 s (was ~160 s) |
https://www.python.org | runtime snapshot | root 98, visual 100, mobile 98, tablet 94 | ~226 s (was ~1011 s, failed at 73) |
https://www.example.com | exact reuse | ready yes | — |
These are generated by the local self-verify pipeline, not manually assigned ratings. Earlier bounded-rebuild previews embedded the reference screenshot, which inflated their visual score; the runtime snapshot renders real DOM and CSS, and every row above was also checked by side-by-side screenshot review. Known gap: layouts that page scripts compute for viewports other than the captured one (for example masonry footers) can still drift at tablet width. The reproducible commands and score thresholds are tracked in docs/benchmark-evidence.json. Production readiness gates are tracked in docs/production-pipeline-gates.json.
X-Frame-Options and CSP-blocked pages by rebuilding from captured evidencenetwork-replay-limited, auth-session-missing, public-app-gate, and canvas-visual-fallbackreplay_readiness before treating captured network evidence as replay-gradenetwork/manifest.json artifactsstorage_state_path or user_data_dir outside the repo1440x1200768x1024390x844The package uses playwright-core; it does not download a browser by itself.
Installing this project adds the source-first-clone plugin bundle, the exact-clone-intake skill, and the MCP server that exposes the URL inspection, capture, rebuild, and verification tools.
npm install -g web-embedding
web-embedding install web-embedding doctor
Clone a public URL after installing:
web-embedding clone \
--url https://developer.mozilla.org/en-US/ \ --output-dir ./.tmp/mdn-clone \ --wait-seconds 2 \ --timeout-seconds 35 \ --breakpoints mobile tablet
If you already have an older local plugin installed, overwrite it with:
web-embedding install --force
web-embedding doctor
You can also run the installer without a global install:
npx web-embedding install
For MCP clients that can launch npm stdio servers:
{
"mcpServers": { "source-first-clone": { "command": "npx", "args": ["-y", "web-embedding@latest", "mcp"] } } }
For local smoke testing:
npx web-embedding@latest mcp
The MCP Registry identity is io.github.jongko54/web-embedding; server.json and package.json#mcpName are kept in sync for registry ownership verification.
The public remote MCP intake endpoint for Apps SDK Developer Mode is:
https://webembedding-jongkos-mcp.vercel.app/mcp
It exposes low-risk source-first routing tools such as URL inspection, embed candidate discovery, clone-mode classification, and embed snippet generation. Full browser capture, HAR replay, queues, bounded rebuilds, and one-pass clone execution remain local-first through the stdio MCP package.
Apps SDK review pages are hosted alongside the endpoint: https://webembedding-jongkos-mcp.vercel.app/privacy.html, https://webembedding-jongkos-mcp.vercel.app/terms.html, and https://webembedding-jongkos-mcp.vercel.app/submission.html.
webEmbedding has two different execution boundaries:
http and https URLs, does not run Playwright, does not read local files, does not use browser profiles or storage state, and does not persist capture artifacts.output_dir or queue_root.storage_state_path or user_data_dir. webEmbedding does not collect credentials, perform login bypasses, or treat a public login shell as private app evidence.needs_session, or sent to manual review unless the user has explicit authorization and supplies the needed evidence.Local URL entrypoints reject non-HTTP schemes such as file:// so an agent cannot use clone/capture tools as a local file reader. Telemetry is disabled by default and, when enabled, excludes target URLs, local paths, captured HTML, screenshots, storage state, environment variables, API keys, and command output.
This repository includes marketplace metadata for the two local agent surfaces:
.agents/plugins/marketplace.json points to ./bundle/source-first-clone..claude-plugin/marketplace.json points to the same bundle and the bundle includes .claude-plugin/plugin.json.Claude Code users can add the marketplace from GitHub with:
/plugin marketplace add jongko54/webEmbedding
/plugin install source-first-clone@webembedding
AI auto-selection expectations and golden prompts live in docs/ai-distribution.md and evals/ai-selection/webembedding-golden-prompts.json.
curl -fsSL https://github.com/jongko54/webEmbedding/releases/latest/download/install.sh | bash
git clone https://github.com/jongko54/webEmbedding.git
cd webEmbedding npm install node ./bin/web-embedding.mjs install node ./bin/web-embedding.mjs doctor
Useful for testing without touching your real agent home:
python3 python/web_embedding/installer.py install --target-home ./.tmp/home
python3 python/web_embedding/installer.py doctor --target-home ./.tmp/home python3 python/web_embedding/installer.py uninstall --target-home ./.tmp/home
Telemetry is disabled by default. On an interactive first install, web-embedding install asks once and defaults to No. Non-interactive installs such as CI and curl | bash do not prompt. If you opt in, web-embedding sends a small anonymous command-completion event to a JSON POST endpoint you control. It does not send target URLs, local paths, captured HTML, screenshots, storage state, environment variables, API keys, or command output.
Enable it during install:
web-embedding install --telemetry --telemetry-endpoint https://your-collector.example/events
Or manage it later:
web-embedding telemetry enable --endpoint https://your-collector.example/events
web-embeddin
Only the beginning is shown; read the rest in the repo