Browser Use vs Auto Browser
A side-by-side look at the Browser Use 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 Browser Use 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 Browser Use 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.
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 | 45/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 118,983 | 914 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Browser Use | View Auto Browser |
Tools & capabilities
Browser Use 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.
Browser Use
{
"mcpServers": {
"browser-use": {
"command": "uvx",
"args": [
"browser-use"
]
}
}
}
Auto Browser
{
"mcpServers": {
"lvcidpsyche-auto-browser": {
"command": "uvx",
"args": [
"auto-browser-mcp"
]
}
}
}
Frequently asked questions
Browser Use is categorized under Browser Automation and uses a local stdio subprocess. Auto Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Browser Use 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.
Browser Use has no declared pricing — check the project's own site. Auth: no auth required. 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 browser-use and lvcidpsyche-auto-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser Use has a quality signal of 45/100 (Fair) with 2 views, 0 installs and 118,983 GitHub stars. Auto Browser has 60/100 (Good) with 4 views, 0 installs and 914 GitHub stars.
