Browsermcp MCP vs Public Browser
A side-by-side look at the Browsermcp MCP and Public Browser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Browsermcp MCP for browser automation work; choose Public 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 Browsermcp MCP when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: No auth required.
Choose Public Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
PUBLIC_BROWSER_SCRIPT_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 40/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | 7,187 | 18 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Browsermcp MCP | View Public Browser |
Tools & capabilities
Browsermcp MCP tools
No tool names declared yet. Check the project README from the listing page.
Public Browser tools 1
PUBLIC_BROWSER_SCRIPT_TOKEN
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.
Browsermcp MCP
No confirmed install command for Browsermcp MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Public Browser
{
"mcpServers": {
"public-browser": {
"command": "npx",
"args": [
"-y",
"public-browser@latest"
]
}
}
}
Frequently asked questions
Browsermcp MCP is categorized under Browser Automation and uses an install path we have not confirmed yet. Public Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Browsermcp MCP for browser automation work and Public 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. Browsermcp MCP has no confirmed install command yet — follow its own setup instructions.
Browsermcp MCP is listed as free. Auth: no auth required. Public Browser 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 browsermcp-mcp and public-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browsermcp MCP has a quality signal of 40/100 (Fair) with 5 views, 0 installs and 7,187 GitHub stars. Public Browser has 57/100 (Good) with 0 views, 0 installs and 18 GitHub stars.
