Siteglass MCP vs Strata

A side-by-side look at the Siteglass MCP and Strata 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 declaredStrata logoStrataBrowser Automation · Local subprocess (stdio)MCP server for progressive tool usage at any scale (see https://klavis.ai)65GreatAuth: not declared

Verdict: choose Siteglass MCP for browser automation work as a local process; choose Strata 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

Strata logoChoose Strata when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like browser_close, browser_resize, browser_console_messages.
Explore Strata

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSiteglass MCP logoSiteglass MCPStrata logoStrata
CategoryBrowser AutomationBrowser Automation
Quality signal51/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsSITEGLASS_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars05,823
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools1025

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

Strata tools 25

  • browser_closeClose the page
  • browser_resizeResize the browser window
  • browser_console_messagesReturns all console messages
  • browser_handle_dialogHandle a dialog
  • browser_emulate_mediaEmulate CSS media features for the page, for example switch between the light and dark color scheme. Omitted parameters are left unchanged; null clears an override.
  • browser_evaluateEvaluate JavaScript expression on page or element
  • browser_file_uploadUpload one or multiple files
  • browser_dropDrop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.
  • browser_findSearch the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.
  • browser_fill_formFill multiple form fields
  • browser_press_keyPress a key on the keyboard
  • browser_typeType text into editable element
  • +13 more on the listing page

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"
      }
    }
  }
}

Strata

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

Frequently asked questions

Siteglass MCP is categorized under Browser Automation and uses a local stdio subprocess. Strata belongs to Browser Automation and uses a local stdio subprocess. Pick Siteglass MCP for browser automation work and Strata 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. Strata has no declared pricing — check the project's own site. 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 strata 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. Strata has 65/100 (Great) with 1 views, 0 installs and 5,823 GitHub stars.