A side-by-side look at the Browser MCP and Ui.Vision MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Browser MCP for browser automation work as a local process; choose Ui.Vision MCP 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 MCP when
You need dedicated capabilities in the Browser Automation domain.
No tool names declared yet. Check the project README from the listing page.
Ui.Vision MCP 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 MCP is categorized under Browser Automation and uses a local stdio subprocess. Ui.Vision MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Browser MCP for browser automation work and Ui.Vision MCP 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 MCP has no declared pricing — check the project's own site. Ui.Vision MCP 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 browser-mcp and ui-vision-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser MCP has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 56 GitHub stars. Ui.Vision MCP has 52/100 (Good) with 0 views, 0 installs and 2,081 GitHub stars.