MCP Browser Dev Tools vs MCP Server Browser
A side-by-side look at the MCP Browser Dev Tools 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 MCP Browser Dev Tools 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 MCP Browser Dev Tools when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
browser_status, ensure_browser, launch_browser.
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 | 53/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 39,344 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 45 | Not listed |
| Full listing | View MCP Browser Dev Tools | View MCP Server Browser |
Tools & capabilities
MCP Browser Dev Tools tools 45
browser_statusensure_browserlaunch_browserlist_tabsnew_tabclose_tabattach_tabdetach_tablist_sessionsnavigatereloadclick- +33 more on the listing page
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.
MCP Browser Dev Tools
{
"mcpServers": {
"mcp-browser-dev-tools": {
"command": "npx",
"args": [
"-y",
"mcp-browser-dev-tools"
]
}
}
}
MCP Server Browser
{
"mcpServers": {
"mcp-server-browser": {
"command": "npx",
"args": [
"-y",
"@agent-tars/cli@latest"
]
}
}
}
Frequently asked questions
MCP Browser Dev Tools 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 MCP Browser Dev Tools 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.
MCP Browser Dev Tools has no declared pricing — check the project's own site. 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 mcp-browser-dev-tools and mcp-server-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Browser Dev Tools has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars. MCP Server Browser has 52/100 (Good) with 2 views, 0 installs and 39,344 GitHub stars.
