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