Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Runs on your computer
TestivAI
What it does
Local-first visual regression for AI agents: verdicts, diff images, explain_snapshot. No API key.
- Connects Runs on your computer
- Account or key No key needed
- Category Design, images & audio
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Install Node.js
One time only; it works for every server that needs Node.js
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "testiv": { "command": "npx", "args": [ "-y", "@testivai/mcp" ] } } }Quit Claude and open it again
Try it
Use TestivAI and tell me what you can do for me, then show me one thing✓ If Claude says it is using TestivAI or shows a TestivAI tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect TestivAI yet
TestivAI runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect TestivAI
- Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
B · Others in Design, images & audio that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Pascal 3D Editor✓ ChatGPT
- Semiotic✓ ChatGPT
- TypeUI✓ ChatGPT
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user testiv -- npx -y @testivai/mcpType /mcp in Claude Code
You should see TestivAI listed as connected
Try it
Use TestivAI and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using TestivAI or shows a TestivAI tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open the AI chat in Cursor in Agent mode
Try it
Use TestivAI and tell me what you can do for me, then show me one thing✓ If Cursor says it is using TestivAI or shows a TestivAI tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open the AI chat in VS Code in Agent mode
Try it
Use TestivAI and tell me what you can do for me, then show me one thing✓ If VS Code says it is using TestivAI or shows a TestivAI tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user testiv -- npx -y @testivai/mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"testiv": {
"command": "npx",
"args": [
"-y",
"@testivai/mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"testiv": {
"command": "npx",
"args": [
"-y",
"@testivai/mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"testiv": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@testivai/mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- GitHub starsi
- 7 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings - Downloads per weeki
- 836/wk
- Verified domain
- ✓ testiv.ai
- Connection
- Runs on your computer
- Latest versioni
- 0.9.4
- Categoryi
- Design, images & audio
- Published to registryi
- Nov 8, 2026
- Code last changedi
- Nov 13, 2026
- Maker
- testivai
- Packages
npm: @testivai/mcp- Website
- github.com
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain testiv.ai (the registry checks domain ownership)
- ✓ Pass
Still maintained
Code last changed today
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Design, images & audioi
- More stars than 78% of the other 3020 servers in this category
- Published to the registry more recently than 85% of the other 3020 servers in this category
- Basic checks equal to or better than 100% of the other 3020 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is TestivAI safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed today, and the latest version (0.9.4) reached the registry 5 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Figma Context MCP, AutoClip, Next AI Draw.io
Others in the same category
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
AutoClip
Clip long videos into short clips with covers and captions. Local CLI and MCP.
Runs on your computer
Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@testivai/mcp
MCP (Model Context Protocol) server that gives AI coding agents eyes on your visual regression results. The agent changes UI code, runs your test suite, then uses these tools to find out what actually changed on screen — and whether it is a real change, likely render noise, or a case the DOM and style signals cannot settle.
Tools
| Tool | What it does |
|---|---|
get_visual_results | Reads visual-report/results.json; when two or more snapshots share one environment change, opens with one line saying so and how many of them are rendering drift; then returns a one-line verdict per snapshot: unhealthy capture (a web font or stylesheet failed to load in the current capture or the baseline, named in the verdict: a glitch of the capture or a broken asset, never noise and never to be approved as a baseline; said before any other reading) / passed (an auto-passed diff says which configured criterion passed it) / size changed (the current capture's dimensions differ from the baseline's: a taller or shorter page is read with the DOM summary and the page shift, and with an identical DOM it is the same content laid out differently, not content added; a width change is the viewport or device scale, not the page; every padded pixel counts as changed, so it is never passed and never noise) / rendering drift (the DOM and computed styles both match and the environment the snapshot was captured in changed since the baseline: a browser build, OS or distro, device scale or capture method, named in the verdict; the machine changed, not the page, so it is never called noise) / likely render noise (the DOM and computed styles both match and the diff is small and scattered; still not proof) / concentrated in one area or large (the DOM and computed styles match, but every diff region fits in a box covering at most a third of the page, or over 1% of pixels differ: a bad capture or a change the style check does not cover, such as size, overflow, transform or an image, so compare the images before approving) / style-only change (identical DOM, different computed styles: a real change) / structural change (with the DOM summary) / styles not compared (identical DOM, style check unavailable: could be render noise or a stylesheet-only change, so compare the images before approving). Snapshots that share an identical signal (style-only change on the same elements, the same page shift, identical DOM with styles not compared, a large spread-out diff, likely render noise) are grouped first; a diff concentrated in one area, or an unhealthy capture, is never grouped. Each missing baseline (committed, but no capture this run) gets its own line (several share one verdict line, so a partial run stays short), with nothing to approve: an intended removal deletes the baseline directory. It ends with the paths to open the HTML report and each diff image |
explain_snapshot | Layered evidence for one snapshot: pixel regions and the shape of the diff (layers.pixel.shape: scattered, concentrated or large), element attribution (which selectors shifted vs changed, whole-page shift), the DOM/style signal, the capture environment (layers.environment: what changed since the baseline, the rendering changes worded, and whether the diff is rendering drift), the capture health (layers.health: what failed to load in each capture and which side is unhealthy), and interpretation guidance; for a missing baseline, status missing, the committed baseline files and what to check instead |
get_report | The raw results.json payload, for agents that parse structured data |
get_diff (alias get_snapshot_diff) | Returns the baseline, current, and diff images for one snapshot so the agent can see the change: the full page downscaled to fit model context (it shows where the changes are), then, when it had to be downscaled, each changed region cropped at native scale with 32 px around it and as wide as the page (up to 1280 px), so text, wrapping and clipping stay readable on a tall full-page capture (up to 3 crops per call, each at most 1280×1024 px and 2,000,000 px in all; nearby regions share a crop, changes come before shifts, a wider area is sampled at 1/2 scale or smaller, a taller one shows its top rows, and after a size change each capture is cut to its own bounds). region (an index the response lists), or y and height (a full-width band), return only that crop; for a missing baseline, the committed baseline image only |
list_baselines | Lists the committed baselines under .testivai/baselines/ |
approve_snapshot / approve_all | Promote reviewed captures to committed baselines (same as testivai approve), only after a human confirms |
The server also ships two prompts. review-visual-changes walks the agent through a full review: summary, explain_snapshot per change, diff images when the evidence is ambiguous, and a recommendation per snapshot. triage-visual-diff (optional snapshot and intent arguments) sorts each diff, and each missing baseline, into glitch, intended change, bug or possible bug, with the evidence and a next step; a changed DOM or changed computed styles is never a glitch, and neither is a missing baseline. The same rules run in CI with the testivai/testivai-oss/review@v1 action.
Approval is a human decision
approve_snapshot and approve_all exist so a human who has looked at a diff can say "approve it" in the conversation and have the agent carry it out. They are not for the agent to decide on its own: approving rewrites what "correct" means, so an agent that approves its own change can launder a regression into the baseline. Both tool descriptions, the review-visual-changes prompt, and every get_visual_results response say so. After approving, commit .testivai/baselines/.
In Claude Code the client enforces this: both approve tools are marked anthropic/requiresUserInteraction, so Claude Code asks you on every approve call, even in auto-approving permission modes. To turn that off, start the server with --no-approval-prompt or set "mcpApprovalPrompt": false in .testivai/config.json (the flag wins); the approve tools then follow your client's own permission settings. Walkthrough: Review and approve in Claude Code.
The other approval paths stay available: npx testivai approve locally, or a /testivai approve comment on the pull request.
Setup
Claude Code
claude mcp add testivai -- npx -y @testivai/mcpCursor / other MCP clients
// .cursor/mcp.json (or your client's equivalent){ "mcpServers": { "testivai": { "command": "npx", "args": ["-y", "@testivai/mcp"] } } }
The server reads the project from its working directory (pass --root to override) and respects reportDir from .testivai/config.json.
Typical agent flow
- Agent edits UI code.
- Agent runs
npx playwright test(the TestivAI reporter captures + diffs). - Agent calls
get_visual_resultsand sees, for example,homepage: changed (4.20% pixels differ) and the DOM changed (2 added, 1 removed, 0 attribute changes) — a real structural change; confirm it is intended before approving. - Agent calls
explain_snapshot homepagefor the evidence, andget_diff homepageto look at the images (the full page, then the changed regions at native scale), then confirms the change matches the task (or fixes its own regression). - Agent reports to the human: what changed, whether it looks intended, and which snapshots need approval. If the human says to approve, the agent calls
approve_snapshot; otherwise the human approves withnpx testivai approveor/testivai approveon the PR.
Local mode only — no account, no API key, nothing leaves the machine.
Full integration guide (instructions-file level, MCP level, zero-test-suite apps, real transcript): docs/guides/ai-agents.md