Agent Browser MCP vs Oculo
A side-by-side look at the Agent Browser MCP and Oculo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Browser MCP for browser automation work as a local process; choose Oculo 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 Agent Browser 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
browser_navigate, browser_go_back, browser_go_forward.
Choose Oculo when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 64/100 · Good | 33/100 · Emerging |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 5 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 34 | Not listed |
| Full listing | View Agent Browser MCP | View Oculo |
Tools & capabilities
Agent Browser MCP tools 34
browser_navigateNavigate to a URL in the browserbrowser_go_backNavigate back in browser historybrowser_go_forwardNavigate forward in browser historybrowser_reloadReload the current pagebrowser_clickClick on an element identified by selector or accessibility propertiesbrowser_fillFill a text input field with the specified valuebrowser_typeType text character by character (useful for triggering key events)browser_hoverHover over an elementbrowser_scrollScroll the page or an elementbrowser_selectSelect an option from a dropdownbrowser_checkCheck a checkbox or radio buttonbrowser_uncheckUncheck a checkbox- +22 more on the listing page
Oculo 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.
Agent Browser MCP
{
"mcpServers": {
"agent-browser-mcp": {
"command": "npx",
"args": [
"-y",
"agent-browser-mcp"
]
}
}
}
Oculo
{
"mcpServers": {
"oculo": {
"command": "npx",
"args": [
"-y",
"electron"
]
}
}
}
Frequently asked questions
Agent Browser MCP is categorized under Browser Automation and uses a local stdio subprocess. Oculo belongs to Browser Automation and uses a local stdio subprocess. Pick Agent Browser MCP for browser automation work and Oculo 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.
Agent Browser MCP is listed as free. Auth: no auth required. Oculo 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 agent-browser-mcp and oculo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Browser MCP has a quality signal of 64/100 (Good) with 6 views, 0 installs and 14 GitHub stars. Oculo has 33/100 (Emerging) with 0 views, 0 installs and 5 GitHub stars.
