Siteglass MCP vs MCP Server Playwright

A side-by-side look at the Siteglass MCP and MCP Server Playwright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Siteglass MCP logoSiteglass MCPBrowser Automation · Local subprocess (stdio)Archive any URL to a shareable rrweb/pdf/png snapshot + agent-driven web QA (scan, run E2E flows).51GoodAuth: not declaredMCP Server Playwright logoMCP Server PlaywrightBrowser Automation · Local subprocess (stdio)An MCP server for browser automation using Playwright61GoodAuth: no auth required

Verdict: choose Siteglass MCP for browser automation work as a local process; choose MCP Server Playwright for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Siteglass MCP logoChoose Siteglass MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SITEGLASS_API_KEY.
  • You want tools like siteglass_scan_local, siteglass_render, siteglass_get_render.
Explore Siteglass MCP

MCP Server Playwright logoChoose MCP Server Playwright when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like browser_navigate, browser_screenshot, browser_click.
Explore MCP Server Playwright

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSiteglass MCP logoSiteglass MCPMCP Server Playwright logoMCP Server Playwright
CategoryBrowser AutomationBrowser Automation
Quality signal51/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsSITEGLASS_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0297
Directory activity 0 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools1010

Tools & capabilities

Siteglass MCP tools 10

  • 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_scancrawl the site → report + findings (first scan free)
  • siteglass_generate_flowsderive executable E2E test flows from a scan
  • siteglass_run_flowrun 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

MCP Server Playwright tools 10

  • browser_navigateNavigate to a URL
  • browser_screenshotTake a screenshot of the current page or a specific element
  • browser_clickClick an element on the page using CSS selector
  • browser_click_textClick an element on the page by its text content
  • browser_fillFill out an input field
  • browser_selectSelect an element on the page with Select tag using CSS selector
  • browser_select_textSelect an element on the page with Select tag by its text content
  • browser_hoverHover an element on the page using CSS selector
  • browser_hover_textHover an element on the page by its text content
  • browser_evaluateExecute JavaScript in the browser console

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Siteglass MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-356": {
      "command": "npx",
      "args": [
        "-y",
        "siteglass-mcp"
      ],
      "env": {
        "SITEGLASS_API_KEY": "YOUR_SITEGLASS_API_KEY_HERE"
      }
    }
  }
}

MCP Server Playwright

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "automatalabs-mcp-server-playwright": {
      "command": "npx",
      "args": [
        "-y",
        "@automatalabs/mcp-server-playwright"
      ]
    }
  }
}

Frequently asked questions

Siteglass MCP is categorized under Browser Automation and uses a local stdio subprocess. MCP Server Playwright belongs to Browser Automation and uses a local stdio subprocess. Pick Siteglass MCP for browser automation work and MCP Server Playwright for browser automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Siteglass MCP has no declared pricing — check the project's own site. MCP Server Playwright is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-356 and automatalabs-mcp-server-playwright as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Siteglass MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Server Playwright has 61/100 (Good) with 3 views, 0 installs and 297 GitHub stars.