Shiplight vs Browser Use MCP Server
A side-by-side look at the Shiplight and Browser Use MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shiplight for browser automation work; choose Browser Use MCP Server 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?
SChoose Shiplight when
- You need dedicated capabilities in the Browser Automation domain.
Choose Browser Use MCP Server when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, CHROME_PATH, PATIENT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Shiplight | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 36/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | OPENAI_API_KEYCHROME_PATHPATIENT |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 847 |
| Directory activity | 2 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Shiplight | View Browser Use MCP Server |
Tools & capabilities
Shiplight tools
No tool names declared yet. Check the project README from the listing page.
Browser Use MCP Server 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.
Shiplight
No confirmed install command for Shiplight yet — follow the setup steps linked from its listing page rather than a guessed package name.
Browser Use MCP Server
{
"mcpServers": {
"co-browser-browser-use-mcp-server": {
"url": "http://localhost:8000/sse"
}
}
}
