Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Visual testing for coding agents: your agent sees every UI change it makes and triages each diff.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://uiverify.ai/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http uiverify https://uiverify.ai/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"uiverify": {
"url": "https://uiverify.ai/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"uiverify": {
"type": "http",
"url": "https://uiverify.ai/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://uiverify.ai/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
게시자(igrlk)가 저장소 소유자(uiverify)가 아니에요. 다른 사람이 등록했을 수 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 0개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.2.0)은 10일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, FOGA node
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Catch unintended UI changes on every pull request. UI Verify renders your components in the cloud, diffs them against a baseline, and lets a coding agent triage what actually changed.
uiverify.ai · GitHub · CLI · Playwright SDK · Vitest SDK · Bun SDK · Skills
UI Verify is a hosted visual-testing service that plugs into your CI. On each PR it:
bun test with the Bun SDK, or from finished screenshots your own harness already produces (native, mobile, React Native) uploaded straight for diffing.This repository holds the open-source client packages, everything that runs in *your* repo. All rendering, diffing, and judging happens server-side; these packages only build a bundle, upload it over HTTP, and read back status, so each is safe to read, fork, and self-host against.
# 1. Install the CLI in your project
npm i -D uiverify
export UIVERIFY_API_KEY=... # from uiverify.ai
npm run build-storybook npx uiverify upload --static-dir storybook-static
Already have screenshots? If your harness already produces them (Detox, Maestro, native snapshot tests, anything), upload the PNGs directly, no Storybook and no rendering required. UI Verify diffs, judges, and baselines them just the same:
npx uiverify upload --screenshots ./screenshots
This is how native, mobile, and React Native projects use UI Verify: each image is keyed by its path under the directory, so a screen maps to the same baseline every build, and you can upload only the screens you changed and carry the rest forward.
Prefer to drive it from your agent? Install the skills (below) and run /uiverify:setup-visual-testing. It detects your capture path, wires CI, and writes the first stories for you.
uiverify checkWhile an agent is editing, it can render just the stories it is touching and diff them against the real CI baseline on the fleet - a "would this pass" answer without waiting for CI:
npm run build-storybook
npx uiverify check --target 'components-button--*' --static-dir storybook-static
It renders only the stories you name (repeatable --target, globs or exact ids), posts no PR check, and never moves a CI baseline. A changed result is informational (exit 0) - review the pixels over the UI Verify MCP (get_build / render_diff_image) and accept in the dashboard or with accept_build to set a branch-scoped preview baseline, so your own accepted changes stop re-flagging on the next check. CI stays the only path to a main baseline.
| Package | Install | What it does |
|---|---|---|
| [`uiverify`](packages/cli) | npm i -D uiverify | The CLI. uiverify upload is the CI uploader (Storybook bundle, Playwright/Vitest/Bun archive, or a directory of finished screenshots) - streams render progress and reflects the visual verdict in its exit code. uiverify check is the agent edit-loop check - renders just the stories you name against the real CI baseline, without posting a check or moving a baseline. |
| [`@uiverify/playwright`](packages/playwright) | npm i -D @uiverify/playwright | The Playwright capture SDK. Swap @playwright/test for it and each test archives its final UI state (serialized DOM + resource bytes) for UI Verify to replay and diff. |
| [`@uiverify/vitest`](packages/vitest) | npm i -D @uiverify/vitest | The Vitest capture SDK. Add uiverifyPlugin() to your Vitest config and each browser-mode test archives its final DOM (serialized DOM + resource bytes) for UI Verify to replay and diff; takeSnapshot() takes named snapshots instead. |
| [`@uiverify/bun`](packages/bun) | bun add -d @uiverify/bun | The Bun capture SDK. Write visual tests on bun test that drive your installed Chrome, and each test archives its final page (serialized DOM + resource bytes) for UI Verify to replay and diff; run() starts your app and runs the test files. |
| [`@uiverify/skills`](packages/skills) | npx skills add, see below | Agent skills: SKILL.md workflows a coding agent runs in your repo to set up visual testing, author economical + deterministic stories, and triage builds. As a Claude Code or Cursor plugin, or a Gemini CLI extension, it also connects the UI Verify MCP server. |
| [`@uiverify/workflow-skills`](packages/workflow-skills) | Claude Code plugin, see below | The agentic-development loop we build UI Verify with: factory, design, review-loop, e2e-verify, babysit-pr, and the skills that tune it. |
Install the skills into any coding agent with one command (skills.sh):
npx skills add uiverify/uiverify
Works in Claude Code, Cursor, Codex, Copilot, Gemini, and any agent that reads a skills folder. Add --list to pick individual skills, and run npx skills update to pull the latest.
Or, on Claude Code, install as a plugin so updates arrive automatically:
/plugin marketplace add uiverify/uiverify
/plugin install uiverify@uiverify
Either way, invoke them by name: /uiverify:setup-visual-testing, /uiverify:triage-visual-changes, and more. See packages/skills for the full list and a copy-in-by-hand alternative.
On Gemini CLI, install the same skills plus the MCP server as an extension, then log in once:
gemini extensions install https://github.com/uiverify/uiverify
In a Gemini CLI session, run /mcp auth uiverify and log in to UI Verify in your browser.
The agentic-development loop we build UI Verify with (factory, design, review-loop, e2e-verify, babysit-pr) is a second plugin in the same marketplace: /plugin install uiverify-workflow@uiverify, then /uiverify-workflow:factory. See packages/workflow-skills.
Connect the UI Verify MCP server and your coding agent (Claude Code, Cursor, Codex, and others) can pull a pull request's UI changes into the conversation, look at each diff, read the AI judge's verdict, and accept the intended baselines - without leaving the terminal.
claude mcp add --scope project --transport http uiverify https://uiverify.ai/mcp
If you installed the plugin above, it already connects this server, so skip the command and just log in from /mcp. Otherwise restart Claude Code after adding it, run /mcp, pick uiverify, and log in to UI Verify in your browser. You log in once and the connection reaches every project in every team you are a member of. --scope project writes it to your committed .mcp.json so the whole team gets it; the file holds no secret, since each teammate logs in with their own account. In Cursor, add { "mcpServers": { "uiverify": { "url": "https://uiverify.ai/mcp" } } } to .cursor/mcp.json and log in from its MCP settings. In Gemini CLI, the extension above connects it, and /mcp auth uiverify logs you in. Full guide: Triage visual changes from your coding agent.
The server is remote (streamable HTTP) - there is nothing to install or run. It exposes:
| Tool | What it does |
|---|---|
list_projects | List the projects you can access, with the projectId to pass when you have several |
list_builds | List recent UI Verify builds |
get_build | Get what changed in a build |
list_build_stories | Page through a build's stories by status |
get_pr_changeset | Get what a PR does to the UI vs its base branch |
list_pr_stories | Page through the PR-vs-base changeset by kind |
get_diff | Per-story diff detail with image URLs |
render_diff_image | Fetch the actual pixels of a story image |
review_diff | Accept, deny, or ignore one story's change |
accept_build | Accept every changed story in a build |
Complete, runnable projects under examples/ — one per capture path. Copy a folder, add a project API key, and it works.
| Example | Capture path |
|---|---|
| [`examples/storybook`](examples/storybook) | Storybook stories (no SDK, upload --static-dir) |
| [`examples/vitest`](examples/vitest) | Vitest browser-mode tests with @uiverify/vitest |
| [`examples/playwright`](examples/playwright) | Playwright end-to-end tests with @uiverify/playwright |
| [`examples/bun`](examples/bun) | Bun visual tests (bun test) with @uiverify/bun |
| [`examples/react-native`](examples/react-native) | Finished screenshots (native / mobile / React Native) with upload --screenshots |
The first four capture a slice of the same Shoppy storefront; the React Native one is a small Expo app driven by Maestro. Each folder has its own CI workflow.
pnpm install
pnpm -r build # CLI builds dist/uiverify.js, playwright builds dist/ pnpm -r test pnpm -r typecheck
The CLI requires UIVERIFY_API_KEY and talks to https://uiverify.ai by default (override with --api-url / UIVERIFY_API_URL for self-host or local dev). See each package's README and DEVELOPMENT.md for internals.
MIT © UI Verify