Visionaire Engine
UnclaimedEyes for AI coding agents: deterministic MCP server that tells the LLM which CSS rule wins, in which file, on which line — and why. Cascade verdicts, blast radius, interaction timelines, pixel-perfect audits.
Install
claude mcp add visionaire -- npx -y visionaire-engineSet up this server
More in Files & Storage
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
25 of 25 tools
Documented tools (25)
From project documentation. A server handshake does not verify each tool’s description or behavior.
annotated_screenshot
Screenshot with numbered marks that equal snapshot uids — or an element-scoped crop via clipTo with padding/scale zoom and optional annotate:false
assert_visual
The verification gate. State rendered-geometry claims (equal heights, alignment, gaps, clipping, colors, z-order — 17 assertion types) → deterministic PASS/FAIL with measured pixels and offending uids; register named suites and re-run them after every edit
capture_proof
Before/after evidence bundles: annotated screenshots + suite verdicts, with a verdict delta proving the fix flipped FAIL → PASS
check_alignment
(deprecated → assertvisual) Group pixel audit: which of N elements is off-alignment by how many px, gap-rhythm outliers, size consistency, N-px grid conformance, pixel-snap warnings
diagnose
One-shot "why does this look broken" — ranked culprits with measured evidence for clipping, overflow, off-center, invisibility, overlap, wrong size
evaluate
Escape hatch: run agent-authored JavaScript in the page and get the JSON result, for the genuinely bespoke case no other tool covers
explain_animations
Animations/transitions touching an element: live census, declared rules with file:line, and a closed "why is it not smooth" ruleset
explain_styles
The wedge. Cascade winner/loser per property with file:line + origin attribution, each winner's blast radius (how many other elements it styles), and a scoped-fix selector for just this element
find_elements
Deterministic search by text, selector, role, or screen region — AND-combined by default, match:"any" for a union, visibleOnly:false to include hidden elements
get_listeners
Event listeners on an element + its ancestors, with handler file:line and capture/passive/once flags
impact_preview
Blast-radius report before editing a shared selector: who else matches, grouped with uids, plus a sandboxed dry-run predicting exactly which elements would change
inject_css
The live fix loop: trial declarations on an element (or a page-wide rule) without touching source — see what changed, converge, write source once, revert
inspect_ancestors
Constraint-chain walk: which ancestor constrains width/overflow/stacking
inspect_element
The "what": box model, computed values, visibility verdict
interact
Drive the UI into a state (open a menu/popup/modal, reveal a tab) and leave it there so you can inspect the new state — reports post-action visibility + box
measure_element
Sub-pixel rendered geometry: content box + true text-ink box (glyph extents) with a centering verdict — "is this × actually centered?"
node_at_point
x,y → element uid + ancestor chain
page_origins
Stylesheet inventory + platform detection (WordPress version, theme, builders, optimizers)
page_snapshot
Pruned, uid-keyed tree of what's visible — geometry, layout hints, invisibility reasons
pick_color
The actual painted pixel (composited truth: gradients, images, opacity) + computed colors + WCAG AA/AAA contrast verdict
pick_element
Human-in-the-loop grounding: DevTools-style hover highlight, the user clicks the element that looks wrong
record_interaction
One interaction → a source-attributed causal timeline: handlers, mutations, cancelled transitions, layout shifts
responsive_sweep
One verification payload across many viewports → a per-viewport verdict matrix ("fixed on desktop, still broken on mobile" caught in one call)
style_diff
Record styles, compare later — verify-my-fix loops
visual_diff
Pixel-diff the live page (or one element) against a mockup PNG or a recorded baseline — MATCH/DIVERGENT with divergent regions mapped back to element uids, optional heatmap artifact
Tool change history
FAQ
Questions about Visionaire Engine MCP Server
- How do I connect Visionaire Engine MCP Server to Claude?
- The listing records `claude mcp add visionaire -- npx -y visionaire-engine` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
- Is Visionaire Engine MCP Server free?
- The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can Visionaire Engine MCP Server do?
- Visionaire Engine MCP Server documents 25 tools to the agent, including annotated_screenshot, assert_visual, capture_proof. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.