MCP Server Browser vs Browsermcp MCP
A side-by-side look at the MCP Server Browser and Browsermcp MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Browser for browser automation work as a local process; choose Browsermcp 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 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.
Choose Browsermcp MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 65/100 · Great | 72/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39,582 | 7,318 |
| Directory activity | 6 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 23 | 1 |
| Full listing | View MCP Server Browser | View Browsermcp MCP |
Tools & capabilities
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
Browsermcp MCP tools 1
browserControls the user's Chrome. Runs one command per line, stopping at the first error. Actions print one ✓ line, reads print their output. Do many steps per call. goto <url> | back | forward | reload click <target> fill <target> "<text>" [--submit] type "<text>" press <key> select <target> "<value>" check <target> | uncheck <target> wait <ms> | wait --text "<text>" | wait <target> tab list | tab new [<url>] | tab select <id> | tab close snapshot [<target>] [-i] [--depth N] find "<text>" get text|value|count|url|title [<target>] screenshot [<target>] eval "<js function>" # runs in the page More (help <command>): scroll, hover, drag, upload, dialog, console, requests, request Targets: e12 (a snapshot ref), getByRole('button', { name: 'Go' }), getByLabel/getByText/getByPlaceholder('…'), or CSS. Quote text with spaces: "like this".
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.
MCP Server Browser
{
"mcpServers": {
"agent-infra-mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-infra/mcp-server-browser"
]
}
}
}
Browsermcp MCP
{
"mcpServers": {
"browsermcp-mcp": {
"command": "npx",
"args": [
"-y",
"@browsermcp/mcp@latest"
]
}
}
}
Frequently asked questions
MCP Server Browser is categorized under Browser Automation and uses a local stdio subprocess. Browsermcp MCP belongs to Browser Automation and uses a local stdio subprocess. Pick MCP Server Browser for browser automation work and Browsermcp 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.
MCP Server Browser is listed as free. Auth: no auth required. Browsermcp MCP 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 agent-infra-mcp-server-browser and browsermcp-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Browser has a quality signal of 65/100 (Great) with 6 views, 0 installs and 39,582 GitHub stars. Browsermcp MCP has 72/100 (Great) with 6 views, 0 installs and 7,318 GitHub stars.
