Log inSubmit server
Siteglass MCP logo

Siteglass MCP

by siteglassio

Scan local apps, archive public pages, and run generated browser QA flows with reports, screenshots, video, and replays.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Siteglass MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-356": {
      "command": "npx",
      "args": [
        "-y",
        "siteglass-mcp"
      ],
      "env": {
        "SITEGLASS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

siteglassio/siteglass-mcp MCP server exposes siteglass.io web inspection and archiving tools through MCP. It can scan a local development app in a browser on the user's machine, render public URLs into rrweb, PDF, or PNG archives, and test verified deployed sites with generated E2E flows. Reach for it after changing an app, when you need a shareable page capture, or when you want agent-driven QA of a site you own. Hosted scans and flow runs use cached or supplied API authentication and prepaid Bitcoin Lightning credits.

Use cases

  • Scan a local app after implementing or changing a feature
  • Archive a public page as an rrweb, PDF, or PNG snapshot
  • Generate E2E flows from a deployed site's scan
  • Run authenticated browser checks against a verified site
  • Review screenshots, video, and replay results from a failed flow

Key features

  • Local browser scanning without authentication
  • Public URL archiving in rrweb, PDF, and PNG
  • Ownership verification for hosted site QA
  • AI-derived executable E2E flows
  • Per-step results with screenshots, video, and replay
  • Polling tools for long-running operations

Tools10

What Siteglass MCP lets your agent do. Expand a tool for its parameters.

Self-reported~194 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · siteglass-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads192Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Tools exposed10Callable tools this server registers over MCP.

How Siteglass MCP works

What siteglassio/siteglass-mcp MCP server does

siteglassio/siteglass-mcp MCP server connects MCP clients to siteglass.io's browser scanning, rendering, and web-QA services. Its local scan tool opens a development URL in a headless browser running on the user's machine and returns crawl findings with a report. Findings can include broken links or assets, browser console errors, accessibility issues, SEO issues, and forms that may need testing.

For public pages, the server can request an archive in one of three formats: an interactive rrweb capture, a single-page PDF, or a full-page PNG. The rrweb result preserves the post-JavaScript DOM and supports selectable text and working links. The archive workflow does not require a CAPTCHA, signup, or ownership check.

The hosted QA workflow is intended for deployed sites that the user owns. It registers a URL, verifies ownership, scans the site, derives executable flows, and runs those flows. Results include step-level pass or fail data, screenshots, video, and an rrweb replay. Credentials can be provided for flows that need a test login.

How it works

Install the package with npx siteglass-mcp, then configure it as an MCP server using the client's stdio configuration. Tool calls with longer processing times return an identifier; corresponding get_* tools retrieve the completed scan, render, or flow run instead of keeping one request open until completion.

The local scan is free and does not require authentication. It can target http://localhost:PORT or another URL reachable from the local machine; the local app is not tunneled to siteglass.io. The first local run downloads a headless Chromium browser, which may take about a minute.

Hosted authentication is created and cached at ~/.siteglass/key unless SITEGLASS_API_KEY is set to use a caller-provided key. The first scan for a site is free. Later scans consume two credits, and flow runs consume one credit; the balance is prepaid in USD through Bitcoin Lightning.

Setup and configuration

Run:

Terminal
npx siteglass-mcp

For Claude Code, add it with:

Terminal
claude mcp add siteglass -- npx siteglass-mcp

For Cursor, Claude Desktop, or Windsurf, add a server entry whose command is npx and whose argument is -y siteglass-mcp. After setup, direct an MCP client to test an application URL with siteglass. Use SITEGLASS_API_KEY when the server should use an existing API key instead of its automatically created and cached key.

Tools and capabilities

  • siteglass_scan_local: crawl and analyze a local or otherwise reachable development app.
  • siteglass_render and siteglass_get_render: create and retrieve public URL archives in rrweb, PDF, or PNG formats.
  • siteglass_register_site and siteglass_verify_site: establish ownership using a DNS TXT record or hosted proof token.
  • siteglass_scan and siteglass_get_scan: scan a verified site and retrieve its report and findings.
  • siteglass_generate_flows: turn scan results into executable E2E flows.
  • siteglass_set_credentials: supply a test login for authenticated checks.
  • siteglass_run_flow and siteglass_get_run: execute a flow and retrieve its pass/fail details and captured artifacts.
  • siteglass_feedback: send feedback to the siteglass team.

Limitations and notes

siteglassio/siteglass-mcp MCP server's hosted QA tools are designed for sites that have completed registration and ownership verification. Public rendering can fail or return an empty capture when the target blocks datacenter IP addresses. The renderer does not produce WARC files. Local scanning requires a browser download on its first run, and hosted scans and flow runs can consume prepaid credits after the free allowance.

The package is MIT licensed. The project is listed in the official MCP Registry as io.siteglass/mcp and publishes machine-discovery documents including an OpenAPI description and agent-skills files.

siteglassio/siteglass-mcp MCP server supports the client setup documented for Claude Code, Cursor, Claude Desktop, and Windsurf; other clients may require equivalent stdio configuration.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Siteglass MCP

siteglassio/siteglass-mcp is an MCP server that connects AI clients to siteglass.io for local app scans, public URL archiving, and hosted web QA. Its main tools crawl apps, create rrweb/PDF/PNG snapshots, generate E2E flows, run them, and return findings, reports, screenshots, video, and replays.

Install it with `npx siteglass-mcp`, then add that command to your MCP client's stdio configuration. The README provides commands for Claude Code and JSON configuration examples for Cursor, Claude Desktop, and Windsurf.

Yes, `siteglass_scan_local` can crawl a local or otherwise reachable development URL in a browser on your machine. It does not tunnel the application to siteglass.io, and the first run downloads a headless Chromium browser.

Call `siteglass_render` with the public URL and request an rrweb, PDF, or PNG result. The tool returns a shareable archive, and `siteglass_get_render` retrieves it after any required Lightning invoice has been paid.

Yes, authenticated flows are supported through `siteglass_set_credentials`. For hosted QA, register and verify the site, scan it, generate flows, and run them; the results include per-step status and captured artifacts.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSiteglass MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-356?style=directory)](https://allmcps.com/mcp/mcp-356)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-356"><img src="https://allmcps.com/api/badge/mcp-356?style=directory" alt="Siteglass MCP on AllMCPs" /></a>