Unbrowser vs Scout
A side-by-side look at the Unbrowser and Scout MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Unbrowser for browser automation work as a local process; choose Scout for browser automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Unbrowser 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.
Choose Scout when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 53/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16 | 14 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Unbrowser | View Scout |
Tools & capabilities
Unbrowser tools
No tool names declared yet. Check the project README from the listing page.
Scout 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.
Unbrowser
{
"mcpServers": {
"protostatis-unbrowser": {
"command": "uvx",
"args": [
"pyunbrowser"
]
}
}
}
Scout
{
"mcpServers": {
"scout-2": {
"url": "https://api.groq.com/openai"
}
}
}
Frequently asked questions
Unbrowser is categorized under Browser Automation and uses a local stdio subprocess. Scout belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick Unbrowser for browser automation work and Scout 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.
Unbrowser is listed as free. Auth: no auth required. Scout 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 protostatis-unbrowser and scout-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Unbrowser has a quality signal of 53/100 (Good) with 5 views, 0 installs and 16 GitHub stars. Scout has 43/100 (Fair) with 1 views, 0 installs and 14 GitHub stars.
