Oculo vs Agent Browser MCP
A side-by-side look at the Oculo and Agent Browser MCP 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 Agent Browser MCP 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 Oculo when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 33/100 · Emerging | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 14 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | Not listed | 34 |
| Full listing | View Oculo | View Agent Browser MCP |
Tools & capabilities
Oculo tools
No tool names declared yet. Check the project README from the listing page.
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
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"
]
}
}
}
Agent Browser MCP
{
"mcpServers": {
"agent-browser-mcp": {
"command": "npx",
"args": [
"-y",
"agent-browser-mcp"
]
}
}
}
Frequently asked questions
Oculo is categorized under Browser Automation and uses a local stdio subprocess. Agent Browser MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Oculo for browser automation work and Agent Browser MCP 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.
Oculo has no declared pricing — check the project's own site. Agent Browser MCP is listed as free. Auth: no auth required. 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 oculo and agent-browser-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Oculo has a quality signal of 33/100 (Emerging) with 1 views, 0 installs and 5 GitHub stars. Agent Browser MCP has 64/100 (Good) with 7 views, 0 installs and 14 GitHub stars.
