
Ui Annotator Mcp
io.github.mcpwarePublished by GitHub account mcpwarev0.1.6Updated Oct 24, 2026
Annotates any web page with hover labels for AI assistants — zero extensions, any browser
Overview
Local MCP server that reverse-proxies a web page and labels its elements, so an assistant and a person share the same element names.
- What you can do
- Open a page through the annotator proxy and get a proxy URL to browse in any browser
- List detected UI elements with names, selectors and positions, and force a rescan after page changes
- Flash-highlight a named element so the user can confirm which one is meant
- Toggle inspect mode remotely, which pauses page interactions and copies element names on click
- Show hover overlays with element name, CSS selector, content preview and dimensions
- When to use it
- Useful when reviewing or iterating on a local web UI with an AI coding assistant and describing which element to change is the hard part. It gives both sides a shared vocabulary of component names instead of vague descriptions or screenshots.
- Requirements
- Runs locally via npx as a Node.js package over stdio. The web app under review must be reachable on a local port; the proxy listens on port 7077 by default, configurable with UI_ANNOTATOR_PORT. No accounts, keys or browser extensions are needed.
Installation
In SourceWeft
- Open Ui Annotator Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
UI Annotator MCP
[npm version] [npm downloads] [license] [GitHub stars] [GitHub forks]
English | 廣東話
Bridge the gap between what you see and what AI can reference — in any browser, zero extensions.
The only tool that puts visible labels on every web element. Hover any element, see its name. Tell your AI assistant "make the sidebar wider" — it knows exactly which element you mean. No screenshots, no CSS selectors, no miscommunication.
Why It Matters
Dramatically improves AI-driven UI design and iteration. The pain: telling AI "move that button next to the search bar" never works because the AI can't see your page. UI Annotator fixes this — hover over any element and its component name appears as a label. Now you say "move SearchButton below NavBar" and Claude edits the right component instantly. No browser extensions, works with any framework. The workflow becomes: open page → hover to identify elements → describe changes using real component names → Claude edits → refresh and repeat. Turns a frustrating back-and-forth into a fluid design loop.
The Problem
When reviewing a web UI with an AI coding assistant, the hardest part isn't the code change — it's describing which element you want changed.
"That thing on the left... the second row... no, the one with the icon..."
You don't know what it's called. The AI doesn't know what you're pointing at. You waste time on miscommunication instead of shipping.
The Solution
Open your page through the annotator proxy. Hover any element — instantly see its name, CSS selector, and dimensions. Now you both speak the same language.
That's it. No browser extensions. No code changes. No setup. Works in Chrome, Firefox, Safari, Edge — any browser.
How It Works
The proxy fetches your page, injects a lightweight annotation script, and serves it back. The script scans the DOM, identifies named elements, and reports them to the MCP server. Your AI assistant queries the server to understand what's on the page.
Features
Hover Annotations
Hover any element to see:
- Element name (pink) — the human-readable identifier
- CSS selector (monospace) — the technical reference
- Content preview — what text the element contains
- Dimensions — width × height in pixels
Inspect Mode
Click the Inspect button in the toolbar (or let your AI toggle it). In inspect mode:
- Click any element → copies its name to clipboard
- All page interactions are paused (clicks don't trigger buttons/links)
- Click Inspect again to return to normal mode
Collapsible Toolbar
The toolbar sits at the top center of the page showing:
- Inspect toggle button
- Element count
- Helpful subtitle explaining what to do
- Collapse button (▲) to minimize when not needed
MCP Tools for AI
Why Not Just Use DevTools?
DevTools is for debugging. UI Annotator is for communication — giving humans and AI a shared vocabulary for UI elements.
Why Not Use Existing Tools?
None of these do what UI Annotator does — live visual labels on every element via reverse proxy:
Feature Comparison
Architecture
Zero external dependencies
- Reverse proxy: Node.js built-in
httpmodule - MCP server:
@modelcontextprotocol/sdk(stdio transport) - Communication: HTTP POST (browser → server) + GET polling (server → browser)
- No WebSocket, no Express, no browser extension
How the proxy works
- User requests
localhost:7077/localhost:3847 - Proxy fetches
http://localhost:3847 - For HTML responses:
- Injects
fetch()/XMLHttpRequestinterceptor (rewrites API paths through proxy) - Rewrites
href="/..."andsrc="/..."attributes to route through proxy - Injects annotation script before
</body>
- Injects
- For non-HTML (CSS, JS, images): passes through directly
- Strips
Content-Security-Policyheaders to allow injected script
How annotation works
- Script scans DOM for elements with
id,class, semantic roles, or interactive roles - On hover: positions overlay border (follows
border-radius) + positions tooltip (always within viewport) - Reports all detected elements to server via
POST /__annotator/elements - Polls
GET /__annotator/commandsevery second for server instructions (highlight, rescan, inspect toggle) MutationObserverauto-rescans when DOM changes
Quick Start
With Claude Code
Manual
Environment Variables
More from @mcpware
License
MIT
Source: README.md at commit 6b89c1c
Tools
0Version history
1- v0.1.6LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts