Browser Gateway vs MCP Server Browser
A side-by-side look at the Browser Gateway and MCP Server 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 Gateway for browser automation work as a local process; choose MCP Server 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 Browser Gateway when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Choose MCP Server Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
browser_click, browser_close, browser_close_tab.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 48/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 18 | 39,368 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 23 |
| Full listing | View Browser Gateway | View MCP Server Browser |
Tools & capabilities
Browser Gateway tools
No tool names declared yet. Check the project README from the listing page.
MCP Server Browser tools 23
browser_clickClick an element on the page, before using the tool, use `browser_get_clickable_elements` to get the index of the element, but not call `browser_get_clickable_elements` multiple timesbrowser_closeClose the browser when the task is done and the browser is not needed anymorebrowser_close_tabClose the current tabbrowser_evaluateExecute JavaScript in the browser consolebrowser_form_input_fillFill out an input field, before using the tool, Either 'index' or 'selector' must be providedbrowser_get_clickable_elementsGet the clickable or hoverable or selectable elements on the current page, don't call this tool multiple timesbrowser_get_download_listGet the list of downloaded filesbrowser_get_markdownGet the markdown content of the current pagebrowser_get_textGet the text content of the current pagebrowser_go_backGo back to the previous pagebrowser_go_forwardGo forward to the next pagebrowser_hoverHover an element on the page, Either 'index' or 'selector' must be provided- +11 more on 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": {
"browser-gateway": {
"command": "npx",
"args": [
"browser-gateway"
]
}
}
}
MCP Server Browser
{
"mcpServers": {
"agent-infra-mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-browser"
]
}
}
}
Frequently asked questions
Browser Gateway is categorized under Browser Automation and uses a local stdio subprocess. MCP Server Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Browser Gateway for browser automation work and MCP Server 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 Gateway has no declared pricing — check the project's own site. MCP Server 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 browser-gateway and agent-infra-mcp-server-browser 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. MCP Server Browser has 67/100 (Great) with 6 views, 0 installs and 39,368 GitHub stars.
