Agent Browser vs Auto Browser
A side-by-side look at the Agent Browser and Auto Browser 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 for browser automation work as a local process; choose Auto Browser 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 when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Choose Auto Browser 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 44/100 · Fair | 60/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 |
Tools & capabilities
Agent Browser tools
No tool names declared yet. Check the project README from the listing page.
Auto Browser 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
{
"mcpServers": {
"agent-browser": {
"command": "npx",
"args": [
"-y",
"aether-browser"
]
}
}
}
Auto Browser
{
"mcpServers": {
"lvcidpsyche-auto-browser": {
"command": "uvx",
"args": [
"auto-browser-mcp"
]
}
}
}
Frequently asked questions
Agent Browser is categorized under Browser Automation and uses a local stdio subprocess. Auto Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Agent Browser for browser automation work and Auto Browser 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 has no declared pricing — check the project's own site. Auto Browser 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 agent-browser and lvcidpsyche-auto-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Browser has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 12 GitHub stars. Auto Browser has 60/100 (Good) with 4 views, 0 installs and 902 GitHub stars.
