Ext Ops Panel
Open dashboard
Comparison

visual-eyes vs SnapRender

visual-eyes is a plugin bundle for AI coding tools published by nikolasdehor. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SnapRender is an MCP server published by User0856. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacevisual-eyesSnapRender
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 3
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.8
Downloads/month (npm): 496
Downloads/week (npm): 309
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

visual-eyes vs SnapRender
Factvisual-eyesSnapRender
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)3 (better)
Forks (GitHub) (differs)3 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nikolasdehor/visual-eyesgithub.com/user0856/snaprender-integrations
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

visual-eyes

In its own words, on Claude Code: claude-plugins-community:

Give Claude Code the ability to see running web applications. Visual Eyes captures screenshots via Playwright, lets Claude analyze the UI visually, auto-fix layout bugs, and run pixel-level regression testing. Works with any localhost app, zero config needed. Supports desktop, mobile, and full-page captures.

SnapRender

In its own words, on Official MCP Registry:

Local stdio MCP server for SnapRender screenshots. Hosted version: com.snap-render.app/snap-render

How to run each

visual-eyes As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install visual-eyes@claude-community

SnapRender As a local MCP server: npm package

Claude Code
claude mcp add --env "SNAPRENDER_API_KEY=<YOUR_SNAPRENDER_API_KEY>" --transport stdio snaprender -- npx -y snaprender-mcp

Requires: SNAPRENDER_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of visual-eyes publish no settings it asks for, so we do not compare settings.

What it can do: visual-eyes · What it can do: SnapRender · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built