It reads source, not the page
Models get HTML and class names. The browser's truth — resolved styles, loaded fonts, JS-built layout, hover and scroll states — never reaches them.
Wibar opens pages in a real browser and measures what actually renders — layout, type, color, motion — for Claude, Cursor or any MCP agent. Then it brings the section you want into your own code, verified against the original.
Wibar is Coming Soon · Private Waitlist
The blind spot
Ask an agent to match a design and it guesses. Not because it's bad at CSS — because nothing it reads tells it what the browser drew.
Models get HTML and class names. The browser's truth — resolved styles, loaded fonts, JS-built layout, hover and scroll states — never reaches them.
A screenshot can't tell 24px from 1.5rem, Inter from Helvetica, or a 700ms ease-out from a cut. So the agent squints — and approximates.
Desktop and mobile, on your machine. Every element's box, every rule that actually applies, every font, asset, hover and scroll state — structured for your agent to read.
Start freeThe difference
Make our pricing section look like the one on that site.
Sure! Here's a three-card pricing section with a gradient highlight, rounded corners and a clean sans-serif…
Make our pricing section look like the one on that site.
⏺ wibar.take_design(target: "pricing") ✓ 148 CSS rules that actually apply ✓ 6 fonts · 14 assets localized⏺ wibar.verify_graft() ✓ 212 elements · 99.3% matchMCP server
Wibar ships as an MCP server and a CLI. One prompt wires it into Claude, Cursor, Codex, Antigravity or any agent.
wibar_analyze_live_pageSee a page: sections, component families, tokens.wibar_inspect_live_regionZoom into one region, with its computed styles.wibar_audit_live_designCatch overflow, broken type scale, tiny tap targets.wibar_take_designBring a section into your project, real CSS included.wibar_verify_graftMeasure the result against the recording.› take the pricing section from example.com
into src/pages/pricing.astro
⏺ wibar.take_design(url: "https://example.com", target: "pricing")
recorded desktop 1440 · mobile 390
markup pricing.astro 212 elements
styles pricing.css 148 rules · 6 fonts
assets pricing.assets/ 14 files
⏺ wibar.verify_graft(pageUrl: "localhost:4321/pricing")
compared 212 elements
match 99.3% 3 values repaired from the recording
✓ Mounted in src/pages/pricing.astro
↳ edit the copy, keep the measurements.How it works
One recording feeds all three — so what lands in your repo is what was on the screen.
Proof
pixel match, full resend.com/login page grafted into a project
graft benchmark · 1440px · Sep 2026visual match on the gsap.com mirror, with 96% of its motion kept
desktop + mobile, offline · Sep 2026extension picks resolved to the exact element the engine measured
4 sites · 2 misses, 0 wrong · Sep 2026bytes of your pages sent to our servers — capture runs locally
we only count your quotaUse cases
Wibar isn't a downloader. It moves your own site, and it turns the best of the web into a starting point you'll make your own.
Move your own site into the stack you choose — components, tokens, assets and motion rebuilt as code you own, not a runtime you rent.
Bring a hero, a pricing table or a login screen from any page into your project, then rewrite it with your agent — copy, brand, images — on top of measured spacing and motion.
Send any page to Figma as editable layers — desktop and mobile frames side by side, scroll motion carried over as keyframes.
Ask your agent what's off: overflow, an inconsistent type scale, heading order, tap targets under 44px — measured on the live page.
Try it free on your sitePoint at any section while you browse and hand it straight to your agent — no URLs to paste, no selectors to write.
Pricing
Every plan includes the MCP server, the CLI and local capture.
Try Wibar on a real page.
For developers shipping interfaces every week.
For teams delivering client sites.
Private API, high volume, priority support.
Prices in USD.
FAQ
Wibar gives AI agents eyes on the web. It opens a page in a real Chromium browser on your machine, measures what actually renders — DOM, computed styles, fonts, assets, interactions and scroll motion — and exposes it to your agent over MCP. When you want a design in your own project, it writes the section's markup and the CSS rules that actually apply, then verifies the result against the recording.
No. A cloner hands you someone else's site. Wibar hands your agent measurements and a starting point it can edit — tokens, readable class names, your framework. Use it to move your own site, and as a reference for sections you'll make your own: replace the copy, brand and images before you ship.
Anything that speaks MCP. wibar mcp install wires it into Claude Desktop, Claude Code, Cursor, Codex, Windsurf, VS Code and Gemini. The same engine runs from the CLI for scripts and CI.
On your machine. The browser runs locally and recordings stay on your disk. Our API only keeps count of your quota.
Wibar doesn't bypass protection. Record the page in your own browser (DevTools → Network → Save all as HAR) and hand the file to Wibar — it rebuilds from your recording without contacting the site.
Sections come out as HTML, Astro, PHP, JSX (React / Next.js) or Vue. Full-site exports target Astro, Next.js, Vue, Laravel and modular PHP.
Early Access
We are currently preparing for private release. Join the waitlist to get early access to the MCP server, CLI, and browser capture engine.
Private beta · Waitlist open
✓You're on the list. We'll write to when your spot opens.
No spam · One email when your spot opens · First capture free