MCP server

Snapvisor runs a remote Model Context Protocol (MCP) server so AI agents can review your UI. Connect once and your agent can list builds, read screenshot diffs, create reviews, and comment — all through the same public API.

Endpoint

The Snapvisor MCP server is a stateless, streamable HTTP endpoint:

https://mcp.snapvisor.io

Opening the endpoint in a browser redirects here, to this guide. Programmatic MCP clients connect over HTTP with a bearer token.

Connect Claude Code

Add the connector with a single command:

claude mcp add --transport http snapvisor https://mcp.snapvisor.io

The first request without a token returns a 401 that triggers the OAuth flow: your browser opens a Snapvisor consent screen, you approve the connection, and the agent is issued a scoped access token. No secrets are pasted into the client.

Connect Cursor and other MCP clients

Any MCP client that speaks streamable HTTP can connect. Point it at the endpoint — for example, in a client that uses an mcpServers config:

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

Authentication

The server accepts two credentials:

• OAuth 2.1 — the default browser-consent flow above. Tokens are issued per client and can be revoked at any time under Settings → Applications in the app.
• Personal access token — mint one under Settings → Tokens and pass it as a bearer header. Useful for headless or CI agents:

# Use a personal access token instead of the OAuth browser flow
claude mcp add --transport http snapvisor https://mcp.snapvisor.io \
  --header "Authorization: Bearer <your personal access token>"

What agents can do

The tool surface is derived automatically from Snapvisor's public REST API, so it always matches what the product can do. The tools fall into four groups:

• Builds and projects — list and inspect builds, projects, and their status across your organization.
• Screenshot diffs — read the visual changes in any build: baseline, current, and the computed diff.
• Reviews and approvals — create reviews to approve or reject visual changes without leaving the agent.
• Comments — read and post build comments so humans and agents stay on the same thread.

Plan requirements