Siteglass MCP vs Browser Use
A side-by-side look at the Siteglass MCP and Browser Use MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Siteglass MCP for browser automation work as a local process; choose Browser Use 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 Browser Use 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 51/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | SITEGLASS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 119,062 |
| Directory activity | 0 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Siteglass MCP | View Browser Use |
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
Browser Use tools
No tool names declared yet. Check the project README from 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"
}
}
}
}
Browser Use
{
"mcpServers": {
"browser-use": {
"command": "uvx",
"args": [
"browser-use"
]
}
}
}
Frequently asked questions
Siteglass MCP is categorized under Browser Automation and uses a local stdio subprocess. Browser Use belongs to Browser Automation and uses a local stdio subprocess. Pick Siteglass MCP for browser automation work and Browser Use 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. Browser Use has no declared pricing — check the project's own site. 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 browser-use 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. Browser Use has 47/100 (Fair) with 7 views, 0 installs and 119,062 GitHub stars.
