Comet MCP vs Siteglass MCP
A side-by-side look at the Comet MCP and Siteglass MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Comet MCP for browser automation work as a local process; choose Siteglass 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 Comet 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
comet_connect, comet_ask, comet_poll.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 59/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SITEGLASS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 180 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 10 |
| Full listing | View Comet MCP | View Siteglass MCP |
Tools & capabilities
Comet MCP tools 6
comet_connectConnect to Comet (auto-starts if needed)comet_askSend a task and wait for responsecomet_pollCheck progress on long-running taskscomet_stopStop current taskcomet_screenshotCapture current pagecomet_modeSwitch modes: search, research, labs, learn
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
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.
Comet MCP
{
"mcpServers": {
"hanzili-comet-mcp": {
"command": "npx",
"args": [
"-y",
"comet-mcp"
]
}
}
}
Siteglass MCP
{
"mcpServers": {
"mcp-356": {
"command": "npx",
"args": [
"-y",
"siteglass-mcp"
],
"env": {
"SITEGLASS_API_KEY": "YOUR_SITEGLASS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Comet MCP is categorized under Browser Automation and uses a local stdio subprocess. Siteglass MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Comet MCP for browser automation work and Siteglass 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.
Comet MCP is listed as free. Auth: no auth required. Siteglass MCP 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 hanzili-comet-mcp and mcp-356 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Comet MCP has a quality signal of 59/100 (Good) with 4 views, 0 installs and 180 GitHub stars. Siteglass MCP has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
