SnapVisor

io.snapvisorPublished by snapvisor.ioOfficial publisherv1.0.2Updated Oct 30, 2026

Visual regression testing over MCP: upload screenshots, review diffs, approve. No CI needed.

VerifiedStreamable HTTPWeb executableDeveloper ToolsMedia & Design

Overview

AI-generated overview

Remote MCP server for visual regression testing: an assistant can upload screenshots, review visual diffs and approve changes without a CI pipeline.

What you can do
  • Upload screenshots for visual comparison
  • Review visual diffs between screenshot versions
  • Approve changes to accept the new baseline
  • Run visual regression checks without a CI pipeline
When to use it
Useful when you want an assistant to check UI screenshots for visual changes and approve or reject them, especially on projects without CI-based visual testing.
Requirements
A remote MCP endpoint at mcp.snapvisor.io over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
OAuth grants the server access to your SnapVisor account, and approving a diff changes the accepted baseline for future comparisons. Screenshots you upload are sent to a third-party service.

Installation

In SourceWeft

  1. Open SnapVisor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.snapvisor%2Fsnapvisor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "snapvisor": {
      "type": "http",
      "url": "https://mcp.snapvisor.io/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 30, 2026
  2. v1.0.1Oct 29, 2026
  3. v1.0.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.