Chrome MCP vs Public Browser
A side-by-side look at the Chrome 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 Chrome MCP for browser automation work as a local process; 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 Chrome MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CHROME_MCP_TOKEN, CHROME_MCP_EXTENSION_DIR.
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 | 47/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CHROME_MCP_TOKENCHROME_MCP_EXTENSION_DIR | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 18 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Chrome MCP | View Public Browser |
Tools & capabilities
Chrome 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.
Chrome MCP
{
"mcpServers": {
"chrome-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-browser-extension@latest"
],
"env": {
"CHROME_MCP_TOKEN": "YOUR_CHROME_MCP_TOKEN_HERE",
"CHROME_MCP_EXTENSION_DIR": "YOUR_CHROME_MCP_EXTENSION_DIR_HERE"
}
}
}
}
Public Browser
{
"mcpServers": {
"public-browser": {
"command": "npx",
"args": [
"-y",
"public-browser@latest"
]
}
}
}
Frequently asked questions
Chrome MCP is categorized under Browser Automation and uses a local stdio subprocess. Public Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Chrome 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.
Chrome MCP has no declared pricing — check the project's own site. 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 chrome-mcp and public-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chrome MCP has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Public Browser has 57/100 (Good) with 0 views, 0 installs and 18 GitHub stars.
