ui-diff-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NVIDIA_API_KEY | No | Your NVIDIA API key (optional) | |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key | |
| NVIDIA_VLM_BASE_URL | No | Base URL for NVIDIA VLM (optional) | |
| LOCATEANYTHING_SIDECAR_URL | No | URL for the sidecar (optional) | http://127.0.0.1:39731 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_ui_imagesC | Compares an expected mobile mockup image against an actual mobile screenshot using only deterministic methods (no visual models). |
| discover_ui_diffsC | Runs full UI diff analysis, including visual model-based target discovery and classification. Compares expected mockup against actual screenshot. |
| ui_diff_model_healthA | Checks health of all visual models used by the diff pipeline. |
| read_ui_diff_reportB | Reads and returns a previously generated UI diff report JSON file. |
| capture_mobile_screenB | Captures a screenshot from a connected mobile device using adb or ios-simctl. |
| start_ui_diff_runA | Starts a UI diff run in the background without holding the MCP request open. Returns a runId to poll with get_ui_diff_run_status. Use this for large or slow audits like Calorix full scans. |
| get_ui_diff_run_statusB | Returns the status of a background UI diff run started by start_ui_diff_run. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools are mostly distinct but compare_ui_images and discover_ui_diffs both compare screenshots; descriptions clarify deterministic vs model-based, but could cause temporary confusion.
Naming is inconsistent: some tools start with verbs (capture, compare, discover, get, read, start) while ui_diff_model_health is a noun phrase. Also mixing ui_diff and ui_diffs, and get vs read.
7 tools is well-scoped for UI diffing: capture, two compare modes, background run management (start, status, report), and health check. No unnecessary tools.
Covers core workflow: capture, compare (sync/async), background run, report retrieval, model health. Minor gap: no tool to list or cancel runs, but not critical.