io.siteglass/mcp

Registre officiel Productivité

Archive any URL to a shareable rrweb/pdf/png snapshot + agent-driven web QA (scan, run E2E flows).

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package siteglass-mcp
Claude Code
claude mcp add io-siteglass-mcp -e 'SITEGLASS_API_KEY=<your siteglass_api_key>' -e 'SITEGLASS_BASE_URL=<SITEGLASS_BASE_URL>' -- npx -y siteglass-mcp@0.1.5
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "io-siteglass-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "siteglass-mcp@0.1.5"
            ],
            "env": {
                "SITEGLASS_API_KEY": "<your siteglass_api_key>",
                "SITEGLASS_BASE_URL": "<SITEGLASS_BASE_URL>"
            }
        }
    }
}

Variables d'environnement

  • SITEGLASS_API_KEY secret siteglass API key (optional; the server auto-creates an account if absent).
  • SITEGLASS_BASE_URL API base URL (default https://siteglass.io).

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. siteglass MCP server
  2. Install
  3. Tools
  4. Discovery

siteglass MCP server

siteglass-mcp exposes siteglass.io as MCP tools. Three things an AI agent (or a human) can do with it:

  1. Scan the app you're building — FREE, no account — siteglass_scan_local runs a headless browser on your machine against http://localhost:PORT (or any URL you can reach — nothing is tunneled to us), then siteglass analyzes the crawl and returns real findings: broken links/assets, console errors, accessibility & SEO issues, forms worth testing, plus a plain-English report. Point it at your dev server right after the agent builds or changes the app. No signup, no ownership verification, no payment. (First run downloads a headless Chromium, ~1 min.)
  2. Archive any public URL — siteglass_render renders a page server-side and returns a permanent, shareable snapshot: an interactive rrweb DOM capture (post-JS, selectable text, working links), a single-page PDF, or a full-page PNG. No CAPTCHA, no signup, no ownership check, callable programmatically — a bot-friendly alternative to archive.today. (It renders JS-heavy pages; it does not produce WARC, and if the target itself blocks datacenter IPs the capture can come back empty.)
  3. Web-QA a deployed site you own — register → verify → scan → generate flows → run → read results, autonomously, no human signup. This is the hosted/continuous tier (runs on our servers against your live site).

The local scan (1) is free and needs no auth. For the hosted tools (2, 3), auth is automatic (creates + caches an API key at ~/.siteglass/key; set SITEGLASS_API_KEY to use your own); the first scan per site is free, then scans (2 credits) and flow runs (1 credit) draw from a prepaid balance topped up in USD over Bitcoin Lightning.

Install

npx siteglass-mcp

Claude Code:

claude mcp add siteglass -- npx siteglass-mcp

Cursor / Claude Desktop / Windsurf — add to the MCP config (~/.cursor/mcp.json, claude_desktop_config.json, …):

{
  "mcpServers": {
    "siteglass": { "command": "npx", "args": ["-y", "siteglass-mcp"] }
  }
}

OpenClaw — add to ~/.openclaw/openclaw.json (OpenClaw consumes MCP servers); your assistant gets the siteglass_* tools:

{ "mcpServers": { "siteglass": { "command": "npx", "args": ["-y", "siteglass-mcp"] } } }

Then ask the agent: "test my app at <url> with siteglass."

Tools

tooldoes
siteglass_scan_localfree, no-auth — crawl a local/dev app in a browser on your machine → analyzed findings + report
siteglass_renderarchive any public URL → shareable snapshot permalink (rrweb / pdf / png); no CAPTCHA, no signup
siteglass_get_renderfetch an archive once its Lightning invoice is paid
siteglass_register_siteregister an app URL, get an ownership-proof token
siteglass_verify_siteconfirm the token is live (DNS TXT or hosted)
siteglass_scan / siteglass_get_scancrawl the site → report + findings (first scan free)
siteglass_generate_flowsderive executable E2E test flows from a scan
siteglass_run_flow / siteglass_get_runrun a flow → per-step pass/fail, screenshots, video, rrweb replay
siteglass_set_credentialsgive a test login for authenticated flows
siteglass_feedbacksend feedback to the siteglass team

Long ops return an id and you poll the get_* tool, so every call stays under MCP client request timeouts.

Discovery

  • Listed in the official MCP Registry as io.siteglass/mcp.
  • Machine-discovery on the API host: https://siteglass.io/openapi.json, /.well-known/agent-skills/index.json, /llms.txt, /SKILLS.md.

MIT licensed.

Questions fréquentes

Qu'est-ce que io.siteglass/mcp ?

Archive any URL to a shareable rrweb/pdf/png snapshot + agent-driven web QA (scan, run E2E flows).

Comment installer io.siteglass/mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add io-siteglass-mcp -e 'SITEGLASS_API_KEY=<your siteglass_api_key>' -e 'SITEGLASS_BASE_URL=<SITEGLASS_BASE_URL>' -- npx -y siteglass-mcp@0.1.5. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.siteglass/mcp ?

Oui. Il attend SITEGLASS_API_KEY, à renseigner dans sa configuration.

io.siteglass/mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.siteglass/mcp ?

Il est publié par siteglassio. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.