D
djig/ui-loop
Context-budgeted visual feedback for coding agents.
★ 1·updated 2026-10-10
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · djig/ui-loop · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
djig/ui-loop;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# ui-loop
Excerpted from the repository README (abridged)
> See the UI your coding agent just changed: structured summaries + diff-only crops in ~300 tokens instead of full screenshots.
Context-budgeted visual feedback for coding agents.
ui-loop is an MCP server, a CLI and a Claude Code plugin that lets a coding agent (Claude Code, Cursor, Codex) see the UI it just changed without flooding its context window. Instead of a full screenshot every turn, the agent gets a short structured text summary (console errors, failed requests, overflow, layout shifts, accessibility violations) plus small crops of only the regions that changed since the last capture, all fitted into a token budget you choose. Captures live on disk under .ui-loop/ with automatic eviction, so nothing accumulates in the conversation.
Real example: full screenshot costs ~1,366 tokens vs ui-loop's ~305 tokens (text summary + one diff crop)
## Why
General-purpose browser automation servers are great at driving a browser. They are not designed to be cheap verification primitives:
Playwright MCP accessibility snapshots run 50–540 KB each, and the maintainers' position is that pruning history is the agent's job, not the server's (microsoft/playwright-mcp #1233).
Claude in Chrome screenshots are re-sent every turn. One report measured 18 screenshots at roughly 279K tokens per call, consuming 17% of a Max plan context window in 5 turns (anthropics/claude-code #27869).
Chrome DevTools MCP tool definitions alone cost about 17k tokens before the agent does anything.
None of them ship the thing a coding agent actually needs after an edit: diff-only crops + structured text + eviction as a single primitive. That is all ui-loop does.
## Install in 60 seconds
### Claude Code (plugin, recommended)
bash
claude plugin marketplace add djig/ui-loop
claude plugin install ui-loop@djig-ui-loop
This registers the MCP server, a PostToolUse hook that diffs the relevant route after you edit a UI file, and a skill that teaches Claude the capture → edit → diff loop.
Plain MCP server without the hook and skill:
bash
claude mcp add ui-loop -- npx -y @djignesh21/ui-loop@0.1.2 serve
### Cursor
Add to .cursor/mcp.json:
json
{ "mcpServers": { "ui-loop": { "command": "npx", "args": ["-y", "@djignesh21/ui-loop@0.1.2", "serve"] } } }
Optional best-effort hook: copy examples/cursor/hooks.json to .cursor/hooks.json.
### Codex
bash
codex mcp add ui-loop -- npx -y @djignesh21/ui-loop@0.1.2 serve
### Any agent that reads mcp.json / plugin.json
The repo root carries an agent-plugins.org plugin.json and mcp.json, so Copilot, Codex and Cursor can install it from the GitHub URL.
### In your project
bash
npx -y @djignesh21/ui-loop@0.1.2 init # adds .ui-loop/ to .gitignore, prints config snippets
Chromium is resolved from UI_LOOP_CHROMIUM, then Playwright's bundled Chromium, then common system paths (Google Chrome, Chromium). If none is found: npx playwright install chromium or set UI_LOOP_CHROMIUM=/path/to/chrome.
## The loop
1. ui_detect_dev_server → http://localhost:3000
2. ui_capture { url, label } before editing (baseline; returns one downscaled full image the first time)
3. Edit the code
4. ui_diff { url, label } → text summary + crops of changed regions within budget
Context-budgeted visual feedback for coding agents.
ui-loop is an MCP server, a CLI and a Claude Code plugin that lets a coding agent (Claude Code, Cursor, Codex) see the UI it just changed without flooding its context window. Instead of a full screenshot every turn, the agent gets a short structured text summary (console errors, failed requests, overflow, layout shifts, accessibility violations) plus small crops of only the regions that changed since the last capture, all fitted into a token budget you choose. Captures live on disk under .ui-loop/ with automatic eviction, so nothing accumulates in the conversation.
Real example: full screenshot costs ~1,366 tokens vs ui-loop's ~305 tokens (text summary + one diff crop)
## Why
General-purpose browser automation servers are great at driving a browser. They are not designed to be cheap verification primitives:
Playwright MCP accessibility snapshots run 50–540 KB each, and the maintainers' position is that pruning history is the agent's job, not the server's (microsoft/playwright-mcp #1233).
Claude in Chrome screenshots are re-sent every turn. One report measured 18 screenshots at roughly 279K tokens per call, consuming 17% of a Max plan context window in 5 turns (anthropics/claude-code #27869).
Chrome DevTools MCP tool definitions alone cost about 17k tokens before the agent does anything.
None of them ship the thing a coding agent actually needs after an edit: diff-only crops + structured text + eviction as a single primitive. That is all ui-loop does.
## Install in 60 seconds
### Claude Code (plugin, recommended)
bash
claude plugin marketplace add djig/ui-loop
claude plugin install ui-loop@djig-ui-loop
This registers the MCP server, a PostToolUse hook that diffs the relevant route after you edit a UI file, and a skill that teaches Claude the capture → edit → diff loop.
Plain MCP server without the hook and skill:
bash
claude mcp add ui-loop -- npx -y @djignesh21/ui-loop@0.1.2 serve
### Cursor
Add to .cursor/mcp.json:
json
{ "mcpServers": { "ui-loop": { "command": "npx", "args": ["-y", "@djignesh21/ui-loop@0.1.2", "serve"] } } }
Optional best-effort hook: copy examples/cursor/hooks.json to .cursor/hooks.json.
### Codex
bash
codex mcp add ui-loop -- npx -y @djignesh21/ui-loop@0.1.2 serve
### Any agent that reads mcp.json / plugin.json
The repo root carries an agent-plugins.org plugin.json and mcp.json, so Copilot, Codex and Cursor can install it from the GitHub URL.
### In your project
bash
npx -y @djignesh21/ui-loop@0.1.2 init # adds .ui-loop/ to .gitignore, prints config snippets
Chromium is resolved from UI_LOOP_CHROMIUM, then Playwright's bundled Chromium, then common system paths (Google Chrome, Chromium). If none is found: npx playwright install chromium or set UI_LOOP_CHROMIUM=/path/to/chrome.
## The loop
1. ui_detect_dev_server → http://localhost:3000
2. ui_capture { url, label } before editing (baseline; returns one downscaled full image the first time)
3. Edit the code
4. ui_diff { url, label } → text summary + crops of changed regions within budget
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/djig-ui-loop/)
- Source
- awesome · https://github.com/djig/ui-loop
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.