AntiBrow vs Shiplight
A side-by-side look at the AntiBrow and Shiplight MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AntiBrow for browser automation work as a local process; choose Shiplight for browser automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AntiBrow when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
SChoose Shiplight when
- You need dedicated capabilities in the Browser Automation domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Shiplight | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 59/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AntiBrow | View Shiplight |
Tools & capabilities
AntiBrow tools
No tool names declared yet. Check the project README from the listing page.
Shiplight 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.
AntiBrow
{
"mcpServers": {
"antibrow": {
"command": "npx",
"args": [
"-y",
"antibrow-relay"
]
}
}
}
Shiplight
No confirmed install command for Shiplight yet — follow the setup steps linked from its listing page rather than a guessed package name.
