MCP Server Browser vs Bowmark
A side-by-side look at the MCP Server Browser and Bowmark 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 Bowmark for browser automation over a hosted endpoint. 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 Bowmark when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
BOWMARK_API_KEY. - You want tools like
get_library, run, report.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 67/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | No auth required |
| Pricing | Free | Not declared |
| Required env vars | None listed | BOWMARK_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39,371 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 23 | 3 |
| Full listing | View MCP Server Browser | View Bowmark |
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
Bowmark tools 3
get_libraryRead the typed function library for a task or a site. Read-only, touches no site, and an unrecognized query returns the index rather than an error.runExecute a short async JavaScript script against the live sites and return `{ ok, result, logs, error, ms }`.reportTell Bowmark what it could not do, or which run came back wrong. Recorded as feedback; retries nothing.
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"
]
}
}
}
Bowmark
{
"mcpServers": {
"bowmark-2": {
"url": "https://api.bowmark.ai/v1/library?query="
}
}
}
Frequently asked questions
MCP Server Browser is categorized under Browser Automation and uses a local stdio subprocess. Bowmark belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick MCP Server Browser for browser automation work and Bowmark 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. Bowmark has no declared pricing — check the project's own site. 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 bowmark-2 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 67/100 (Great) with 6 views, 0 installs and 39,371 GitHub stars. Bowmark has 64/100 (Good) with 2 views, 0 installs and 1 GitHub stars.
