Camoufox MCP vs Firefox DevTools MCP
A side-by-side look at the Camoufox 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 Camoufox 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 Camoufox MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_session, list_sessions, save_session.
Choose Firefox DevTools MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- 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 | 52/100 · Good | 69/100 · Great |
| 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 | 7 | 506 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 35 | 35 |
| Full listing | View Camoufox MCP | View Firefox DevTools MCP |
Tools & capabilities
Camoufox MCP tools 35
create_sessionCreate a new isolated session, optionally pre-loading cookies/localStorage from a JSON filelist_sessionsList all sessions with their page counts and metadatasave_sessionExport a session's cookies and localStorage to a JSON fileclose_sessionClose a session and all its pageslist_context_filesList available context files registered in settingsnew_pageCreate a new page, optionally in a specific sessionlist_pagesList all open pages with their session IDsselect_pageSet a page as activeclose_pageClose a pagenavigate_pageNavigate to URL, back, forward, or reloadclickClick an element by UIDhoverHover over an element- +23 more on the listing page
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.
Camoufox MCP
{
"mcpServers": {
"camoufox-mcp": {
"command": "npx",
"args": [
"-y",
"camoufox-mcp"
]
}
}
}
Firefox DevTools MCP
{
"mcpServers": {
"firefox-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Camoufox 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 Camoufox 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.
Camoufox MCP has no declared pricing — check the project's own site. Firefox DevTools MCP 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 camoufox-mcp and firefox-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Camoufox MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 7 GitHub stars. Firefox DevTools MCP has 69/100 (Great) with 3 views, 0 installs and 506 GitHub stars.
