Log inSubmit server
Uiverify logo

Uiverify

Triage pull request visual changes, inspect rendered diffs, and manage baselines through an MCP-connected coding agent.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Uiverify

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "uiverify": {
      "command": "npx",
      "args": [
        "-y",
        "uiverify"
      ],
      "env": {
        "UIVERIFY_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y uiverify

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

The uiverify MCP server connects coding agents to UI Verify’s hosted visual-testing service over streamable HTTP. It lets agents inspect pull request and build changes, view per-story image diffs, read verdicts, and review or accept baselines. Reach for it when CI has uploaded Storybook, Playwright, Vitest, or finished screenshot results and you want to investigate them from an agent session. The server is remote, so there is no local MCP process to install or run.

Use cases

  • Inspect visual changes reported for a pull request
  • Review per-story image diffs from a build
  • Classify intended UI changes before accepting them
  • Accept all changed stories after a verified visual update

Key features

  • Lists recent UI Verify builds
  • Compares pull-request UI changes with a base branch
  • Shows story-level diff details and rendered pixels
  • Supports accept, deny, and ignore reviews
  • Accepts all changed stories in a build
  • Uses remote streamable HTTP with bearer authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · uiverify (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars23Stargazers on the source repository.
npm downloads2kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Uiverify works

What uiverify MCP server does

The uiverify MCP server brings UI Verify visual-test results into a coding agent’s conversation. UI Verify renders captured interface states in the cloud, compares them with a baseline from the default branch, and reports the result for a pull request. The MCP layer is focused on investigation and review rather than capturing or rendering the application locally.

An agent can use it to understand which stories changed, distinguish the affected states in a build or pull request, inspect image differences, and act on the result. Reviews can be made for individual stories, or all changed stories in a build can be accepted together when the change is intentional.

How it works

Your CI or local workflow first sends visual-test input to UI Verify. Supported inputs include a Storybook static build, archives produced through the Playwright or Vitest capture SDKs, and directories of finished screenshots. UI Verify performs the rendering and comparison on its service, then exposes the resulting builds and pull-request changes through a remote MCP endpoint.

The server uses streamable HTTP at https://uiverify.ai/api/mcp. Authentication is supplied with a bearer token sourced from the UIVERIFY_API_KEY environment variable. Because the server is hosted, the repository’s open-source packages are not required just to connect an agent to the MCP tools.

Setup and configuration

Add the remote server to a compatible agent with the MCP configuration command shown in the project documentation:

Terminal
claude mcp add --scope project --transport http uiverify https://uiverify.ai/api/mcp \
  --header 'Authorization: Bearer ${UIVERIFY_API_KEY}'

Using project scope places the configuration in a committed .mcp.json, while keeping the API key in an environment variable instead of the file. The account key comes from uiverify.ai. The service URL can be overridden for self-hosted or local development through UIVERIFY_API_URL in the broader CLI setup, but the MCP example uses the hosted endpoint.

Tools and capabilities

The uiverify MCP server exposes tools for the following operations:

  • List recent visual-test builds.
  • Retrieve the changes recorded in a build.
  • Page through stories in a build and filter them by status.
  • Compare a pull request’s UI with its base branch.
  • Page through stories in a pull-request changeset by change kind.
  • Get per-story diff details and image URLs.
  • Fetch the rendered pixels for a story image.
  • Accept, deny, or ignore one story’s visual change.
  • Accept every changed story in a build.

These capabilities support agent-led triage, including examining the actual diff image before deciding whether a baseline should change.

Limitations and notes

The uiverify MCP server does not capture application states or perform the cloud rendering itself. Those steps depend on UI Verify’s CLI, capture SDKs, or screenshot upload workflow and must produce builds that the agent can inspect. The check command can provide mid-edit feedback, but its changed result is informational and does not post a pull-request check or move the CI baseline.

Baseline acceptance is consequential: accepting a build changes the baselines represented by that build, while CI remains the path for the main baseline. The provided MCP setup is for a remote service, so network access to the endpoint and a valid API key are required.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Uiverify

uiverify is an MCP server that connects coding agents to UI Verify’s hosted visual-testing service over streamable HTTP. Its main tools list recent builds, inspect build and PR changes, page through stories, retrieve diffs and pixels, review individual changes, and accept all changed stories in a build.

You do not install or run it locally; add the hosted streamable-HTTP endpoint to your MCP client. For Claude Code, use the documented `claude mcp add` command with `https://uiverify.ai/api/mcp` and provide the `UIVERIFY_API_KEY` bearer token.

Yes, the README names Cursor as a supported coding agent. Configure Cursor to connect to the remote UI Verify MCP endpoint and supply the API key through the `UIVERIFY_API_KEY` environment variable.

Use the MCP tools to find the relevant build or pull-request changeset, inspect story-level diffs, and render the actual diff image. Then use `review_diff` to accept, deny, or ignore one story, or use `accept_build` for all changed stories in a build.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUiverify AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/uiverify?style=directory)](https://allmcps.com/mcp/uiverify)
HTML Embed
<a href="https://allmcps.com/mcp/uiverify"><img src="https://allmcps.com/api/badge/uiverify?style=directory" alt="Uiverify on AllMCPs" /></a>