Browser Use MCP Server vs Browser
A side-by-side look at the Browser Use MCP Server and 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 MCP Server for browser automation work over a hosted endpoint; choose Browser for browser automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Browser Use MCP Server when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY, CHROME_PATH, PATIENT.
Choose Browser when
- You need dedicated capabilities in the Browser Automation domain.
- 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 | 55/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | OPENAI_API_KEYCHROME_PATHPATIENT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 846 | 36,641 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Browser Use MCP Server | View Browser |
Tools & capabilities
Browser Use MCP Server tools
No tool names declared yet. Check the project README from the listing page.
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 MCP Server
{
"mcpServers": {
"co-browser-browser-use-mcp-server": {
"url": "http://localhost:8000/sse"
}
}
}
Browser
No confirmed install command for Browser yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Browser Use MCP Server is categorized under Browser Automation and uses a remote HTTP/SSE transport. Browser belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Browser Use MCP Server for browser automation work and 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 has no confirmed install command yet — follow its own setup instructions.
Browser Use MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 co-browser-browser-use-mcp-server and lightpanda-io-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser Use MCP Server has a quality signal of 55/100 (Good) with 6 views, 0 installs and 846 GitHub stars. Browser has 43/100 (Fair) with 0 views, 0 installs and 36,641 GitHub stars.