MCP.Market

One Shot UI MCP server

by TN0123·io.github.TN0123/one-shot-ui·v0.7.0·5 stars

Deterministic UI extraction and screenshot diffing for AI coding agents.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

5 stars97 downloads/wk

Reviews

Write one

Nobody has reviewed One Shot UI yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

One Shot UI tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • compare

    Deterministically diff an implementation screenshot against a reference screenshot. Returns a

  • extract

    Analyze a single reference screenshot into structured data an agent can build from: layout regions

  • plan

    Generate a suggested implementation plan (layout strategy, CSS primitives, repeated patterns,

  • suggest_fixes

    Diff a build against a reference and return concrete, ranked fix observations (size, color, shadow,

  • tokens

    Extract design tokens (color palette, spacing scale, radii) from a reference screenshot.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 71 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How One Shot UI compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
5
more than 83% of 28,688 servers
Downloads a week
97
more than 62% of 12,191 servers with a package

What its tools let an agent do: 5 read

Install One Shot UI in Claude Code, Cursor or VS Code

Runs npx -y one-shot-ui on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add one-shot-ui -- npx -y one-shot-ui
Add to Cursor

What the publisher says

From the One Shot UI repository's README, as published. We do not edit it. Read it on GitHub

one-shot-ui

Catch what the eye can't.

Deterministic screenshot diffing for AI coding agents. Turn a reference screenshot into structured data, diff any build against it — pixel, layout, color, and type — then get the exact CSS to fix. Or copy a UI's design language onto a brand-new screen.

The problem

AI agents get UI ~90% of the way there — then stall. The layout looks right, but a card is 8px too tall, a panel is the wrong shade of gray, a shadow is flat, a gap is off by 24px. Asking the model to "look at the screenshot again and fix it" is slow, and you get a different answer every time.

one-shot-ui closes that last 10% deterministically. It extracts structured data from a reference screenshot — layout regions, colors, typography, spacing, design tokens — diffs your implementation against it, and returns specific, ranked fixes, not "make it look more like this."

Set width to 616px (currently 640px)
Change the fill color to #303040.
Set box-shadow to -3px 0px 24px 0px rgba(28, 29, 38, 0.32).
gap: 176px; /* currently ~152px */

Copy-paste CSS, ranked by visual impact — every example above is real output from the run below.

Watch it converge

The run command loops extract → capture → compare → fix until the heatmap goes quiet. In the run above, the agent's first build looked identical to the eye — one-shot-ui flagged 15 concrete deltas (position, size, color, shadow, spacing) and the loop drove the build to ~2.5% pixel mismatch, within ~0.5% of the tool's own estimated irreducible floor (≈2%, sub-pixel font rendering) for this design.

Why one-shot-ui

  • Deterministic, not vibes. Stable pixel + structural diff scores — same input, same numbers — so you can gate CI on "is this pixel-close enough?"
  • Exact fixes, not nudges. It returns concrete CSS (width: 616px, #303040, gap: 176px), grouped by component and ranked by visual impact.
  • Structural, not just pixels. Detects missing/extra elements, position & size shifts, color, shadow, spacing, and typography — and labels which differences are irreducible (anti-aliasing, photographic content) so agents don't chase ghosts.
  • Not gameable. converge scores structural fidelity — is the reference's content present, placed, and legible? — not just pixel mismatch, and it refuses to win pixels by hiding, overlapping, or recoloring text into its background. It even flags reference text your build renders but clips out of view (a fixed-height overflow:hidden box) — the failure a pixel diff rewards, because cropped text lowers the mismatch.
  • Agent-native. Ships an AGENTS.md (auto-discovered by Claude Code, Cursor, Codex, …) plus a Claude Code skill, so your agent drives it without hand-holding.
  • Local & private. Pixel diffing, OCR, and layout extraction all run on your machine. No images leave your box, no API keys.

Copy a UI's style, not just match it

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

One Shot UI: common questions

Is One Shot UI MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the One Shot UI safety report
How do I install One Shot UI?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does One Shot UI need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is One Shot UI maintained?
The last commit was 109 days ago (2026-07-18). The latest release is v0.7.0.
How does One Shot UI compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.