WebEmbedding
Clone a live URL into source-first assets, rebuild the UI in your stack, and verify pixel or layout fidelity before you ship a landing page or marketing site.
Overview
io.github.jongko54/web-embedding is a Build-phase MCP server that source-first clones URLs, captures pages, rebuilds UI, and verifies fidelity against the original.
What is this MCP server?
- Source-first URL clone, capture, rebuild, and fidelity verification in one MCP toolkit
- Remote streamable-http endpoint plus npm stdio package (web-embedding 0.3.8)
- Stdio transport via `mcp` positional argument for local Claude Code and Cursor
- Designed for comparing rebuilt output against the original URL fidelity
- Server version 0.3.8
- Dual transport: npm stdio and streamable-http remote
- Four capability themes: clone, capture, rebuild, fidelity verification (from description)
Community signal: 2 GitHub stars.
What problem does it solve?
Rebuilding a reference site by hand from screenshots is slow and you cannot tell whether your version actually matches the live page.
Who is it for?
Indie builders cloning a competitor landing page, porting a marketing site into a component framework, or sanity-checking a redesign before ship.
Skip if: Teams that only need passive page scraping without rebuild or fidelity workflows, or projects with no web UI at all.
What do I get? / Deliverables
Your agent can capture a URL into source-oriented artifacts, guide a rebuild, and run fidelity checks so your shipped UI aligns with the reference.
- Captured source-oriented artifacts from a target URL
- Rebuild-oriented workflow the agent can follow in your repo
- Fidelity verification pass against the live or captured reference
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server’s core loop is capture-from-URL, rebuild, and fidelity check—work you do while implementing interfaces, not while ideating alone. frontend fits source-first clone and rebuild workflows that mirror production pages in HTML/CSS/component form.
How it compares
Browser-automation MCP for clone-and-rebuild, not a generic SEO or analytics integration.
Common Questions / FAQ
Who is web-embedding for?
Solo and indie builders using Claude Code, Cursor, or similar agents who need URL-driven capture, rebuild, and fidelity verification for web UIs.
When should I use web-embedding?
Use it when you have a target URL and want source-first capture, a structured rebuild path, and verification that your implementation matches the original.
How do I add web-embedding to my agent?
Add the npm package web-embedding with stdio transport and the `mcp` positional argument, or point your client at the streamable-http remote https://webembedding-mcp.vercel.app/mcp per server.json.