Siteglass MCP vs Playwright MCP
A side-by-side look at the Siteglass MCP and Playwright MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Playwright MCPBrowser Automation · Local subprocess (stdio)Official Microsoft Playwright MCP server, enabling LLMs to interact with web pages through structured accessibility snapshots89ExcellentAuth: no auth requiredVerdict: choose Siteglass MCP for browser automation work as a local process; choose Playwright MCP 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?
Choose 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.
Choose Playwright MCP 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_close, browser_resize, browser_console_messages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Playwright MCP | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 51/100 · Good | 89/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SITEGLASS_API_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 38,558 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 10 | 25 |
| Full listing | View Siteglass MCP | View Playwright MCP |
Tools & capabilities
Siteglass MCP tools 10
siteglass_scan_localfree, no-auth** — crawl a local/dev app in a browser on your machine → analyzed findings + reportsiteglass_renderarchive any public URL → shareable snapshot permalink (rrweb / pdf / png); no CAPTCHA, no signupsiteglass_get_renderfetch an archive once its Lightning invoice is paidsiteglass_register_siteregister an app URL, get an ownership-proof tokensiteglass_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 scansiteglass_run_flowrun a flow → per-step pass/fail, screenshots, video, rrweb replaysiteglass_set_credentialsgive a test login for authenticated flowssiteglass_feedbacksend feedback to the siteglass team
Playwright MCP tools 25
browser_closeClose the pagebrowser_resizeResize the browser windowbrowser_console_messagesReturns all console messagesbrowser_handle_dialogHandle a dialogbrowser_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 elementbrowser_file_uploadUpload one or multiple filesbrowser_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 fieldsbrowser_press_keyPress a key on the keyboardbrowser_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": {
"mcp-356": {
"command": "npx",
"args": [
"-y",
"siteglass-mcp"
],
"env": {
"SITEGLASS_API_KEY": "YOUR_SITEGLASS_API_KEY_HERE"
}
}
}
}
Playwright MCP
{
"mcpServers": {
"microsoft-playwright-mcp": {
"command": "npx",
"args": [
"-y",
"@playwright/mcp@latest"
]
}
}
}
Frequently asked questions
Siteglass MCP is categorized under Browser Automation and uses a local stdio subprocess. Playwright MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Siteglass MCP for browser automation work and Playwright MCP 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. Playwright MCP 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 microsoft-playwright-mcp 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. Playwright MCP has 89/100 (Excellent) with 8 views, 0 installs and 38,558 GitHub stars.