Autobrowserapproval MCP vs Auto Browser
A side-by-side look at the Autobrowserapproval MCP 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 Autobrowserapproval MCP for browser automation work over a hosted endpoint; 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 Autobrowserapproval MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
request_page_approval, read_session_state, submit_approval_result.
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 | 48/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 0 | 914 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Autobrowserapproval MCP | View Auto Browser |
Tools & capabilities
Autobrowserapproval MCP tools 4
request_page_approvalread_session_statesubmit_approval_resultexport_approval_receipt
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.
Autobrowserapproval MCP
{
"mcpServers": {
"autobrowserapproval-mcp": {
"url": "https://autobrowserapproval.clauxel.com/mcp"
}
}
}
Auto Browser
{
"mcpServers": {
"lvcidpsyche-auto-browser": {
"command": "uvx",
"args": [
"auto-browser-mcp"
]
}
}
}
Frequently asked questions
Autobrowserapproval MCP is categorized under Browser Automation and uses a remote HTTP/SSE transport. Auto Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Autobrowserapproval MCP 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.
Autobrowserapproval MCP 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 autobrowserapproval-mcp and lvcidpsyche-auto-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Autobrowserapproval MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Auto Browser has 60/100 (Good) with 4 views, 0 installs and 914 GitHub stars.
