Bowmark vs MCP Server Browser
A side-by-side look at the Bowmark 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 Bowmark for browser automation work over a hosted endpoint; 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 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.
Choose MCP Server Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 64/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | BOWMARK_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 39,379 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Bowmark | View MCP Server Browser |
Tools & capabilities
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.
MCP Server Browser 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.
Bowmark
{
"mcpServers": {
"bowmark-2": {
"url": "https://api.bowmark.ai/v1/library?query="
}
}
}
MCP Server Browser
{
"mcpServers": {
"mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-tars/cli@latest"
]
}
}
}
Frequently asked questions
Bowmark is categorized under Browser Automation and uses a remote HTTP/SSE transport. MCP Server Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Bowmark 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.
Bowmark has no declared pricing — check the project's own site. Auth: no auth required. MCP Server Browser 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 bowmark-2 and mcp-server-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bowmark has a quality signal of 64/100 (Good) with 2 views, 0 installs and 1 GitHub stars. MCP Server Browser has 52/100 (Good) with 2 views, 0 installs and 39,379 GitHub stars.
