Log inSubmit server

Browser Gateway vs Ui.Vision MCP

A side-by-side look at the Browser Gateway 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.

Browser Gateway logoBrowser GatewayBrowser Automation · Local subprocess (stdio)AI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover.48FairAuth: not declaredUi.Vision MCP logoUi.Vision MCPBrowser Automation · Local subprocess (stdio)MCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input52GoodAuth: not declared

Verdict: choose Browser Gateway 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?

Browser Gateway logoChoose Browser Gateway when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Browser Gateway

Ui.Vision MCP logoChoose Ui.Vision MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore Ui.Vision MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrowser Gateway logoBrowser GatewayUi.Vision MCP logoUi.Vision MCP
CategoryBrowser AutomationBrowser Automation
Quality signal48/100 · Fair52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars182,086
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Browser Gateway View Ui.Vision MCP

Tools & capabilities

Browser Gateway tools

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 Gateway

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "browser-gateway": {
      "command": "npx",
      "args": [
        "browser-gateway"
      ]
    }
  }
}

Ui.Vision MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ui-vision-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "uivision-mcp-bridge"
      ]
    }
  }
}

Frequently asked questions

Browser Gateway 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 Gateway 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 Gateway 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-gateway and ui-vision-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Browser Gateway has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 18 GitHub stars. Ui.Vision MCP has 52/100 (Good) with 2 views, 0 installs and 2,086 GitHub stars.

Popular comparisons with Browser Gateway

Popular comparisons with Ui.Vision MCP