Browser Use MCP Server vs Uindow
A side-by-side look at the Browser Use MCP Server and Uindow 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 Uindow 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 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 Uindow when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 55/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | OPENAI_API_KEYCHROME_PATHPATIENT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 847 | 7 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Browser Use MCP Server | View Uindow |
Tools & capabilities
Browser Use MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Uindow 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"
}
}
}
Uindow
{
"mcpServers": {
"uindow": {
"command": "npx",
"args": [
"-y",
"@uindow/cli@latest"
]
}
}
}
Frequently asked questions
Browser Use MCP Server is categorized under Browser Automation and uses a remote HTTP/SSE transport. Uindow belongs to Browser Automation and uses a local stdio subprocess. Pick Browser Use MCP Server for browser automation work and Uindow 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 MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Uindow 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 co-browser-browser-use-mcp-server and uindow 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 5 views, 0 installs and 847 GitHub stars. Uindow has 39/100 (Fair) with 0 views, 0 installs and 7 GitHub stars.