Browsermcp MCP vs Firefox DevTools MCP
A side-by-side look at the Browsermcp MCP and Firefox DevTools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Browsermcp MCP for browser automation work as a local process; choose Firefox DevTools 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 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.
Choose Firefox DevTools 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
list_pages, new_page, navigate_page.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 72/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 | 7,318 | 556 |
| Directory activity | 6 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 1 | 35 |
| Full listing | View Browsermcp MCP | View Firefox DevTools MCP |
Tools & capabilities
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".
Firefox DevTools MCP tools 35
list_pagesList open tabs (index, title, URL). Selected tab is marked.new_pageOpen new tab at URL. Returns tab index.navigate_pageNavigate selected tab to URL.select_pageSelect active tab by index, URL, or title. Index takes precedence.close_pageClose tab by index.get_page_textGet the visible text of the page (document.body.innerText). Caps at maxLength (default 20000 chars); saveTo saves the full text to a file.take_snapshotCapture DOM snapshot with stable UIDs. A UID stays valid across snapshots until its element is removed or the page navigates. Output caps at maxLines (default 100); scope with selector or dump the full tree with saveTo.resolve_uid_to_selectorResolve UID to CSS selector. Fails if the element is gone.clear_snapshotClear snapshot UIDs. Usually not needed.click_by_uidClick element by UID. Set dblClick for double-click.hover_by_uidHover over element by UID.fill_by_uidFill text input/textarea by UID.- +23 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.
Browsermcp MCP
{
"mcpServers": {
"browsermcp-mcp": {
"command": "npx",
"args": [
"-y",
"@browsermcp/mcp@latest"
]
}
}
}
Firefox DevTools MCP
{
"mcpServers": {
"firefox-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Browsermcp MCP is categorized under Browser Automation and uses a local stdio subprocess. Firefox DevTools MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Browsermcp MCP for browser automation work and Firefox DevTools 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.
Browsermcp MCP is listed as free. Auth: no auth required. Firefox DevTools 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 browsermcp-mcp and firefox-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browsermcp MCP has a quality signal of 72/100 (Great) with 6 views, 0 installs and 7,318 GitHub stars. Firefox DevTools MCP has 72/100 (Great) with 10 views, 0 installs and 556 GitHub stars.
