Camoufox MCP vs Public Browser
A side-by-side look at the Camoufox MCP and Public Browser 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 Public 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 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 Public Browser when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
virtual_desk, view_page, click.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 52/100 · Good | 64/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 | 7 | 19 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 35 | 25 |
| Full listing | View Camoufox MCP | View Public Browser |
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
Public Browser tools 25
virtual_deskList all open tabs with IDs, URLs and state. Call it first in every session, after a reconnect, or when unsure; reuse a listed tab ID instead of opening duplicates. Cheap, call liberally.view_pageSee what is on the page: text plus stable element refs for click/type/fill_form. Default filter 'interactive' lists actionable elements; for paragraphs or table cells call view_page(ref, filter: 'all'). Collapsed containers show as [eXX role, N items] — expand with view_page(ref: 'eXX', filter: 'all').clickClick an element by ref, CSS selector, visible text, or viewport x/y (canvas, pixel-precise targets). Dispatches real CDP mouse events. A click that opens a new tab is reported in the response. The DOM diff (NEW/REMOVED/CHANGED) arrives with the next page action, or here with wait_for_diff: true.typeType text into an input identified by ref or CSS selector. For 2+ fields use fill_form; for special keys (Enter, Escape, Tab, arrows) or shortcuts (Ctrl+K) use press_key.fill_formFill a whole form in one call: text inputs, <select> (by value or visible label), checkboxes (boolean) and radio buttons. One round-trip; partial errors do not abort and each field reports its own status. On per-field errors call view_page and retry the failing fields.press_keyPress a key or shortcut (Enter, Escape, Tab, arrows, Ctrl+K). Optionally focus an element first via ref or selector.scrollScroll the page, a container, or an element into view. Reports the position and content growth (scrollHeight delta — detects lazy-loaded content) and handles settle timing. Use container_ref/container_selector plus direction to scroll inside a container.dragDrag a source onto a target: HTML5 drag-and-drop (draggable lists, SortableJS, React DnD) and mouse drags (sliders, canvas, resize handles). Scrolls the source into view; says when no page reaction was detected. Source: from_ref/from_selector or from_x+from_y; target: to_ref/to_selector or to_x+to_y.navigateNavigate the active tab to a URL, or action 'back' / 'reload' (all refs become stale after reload). Waits for settle. Overwrites the user's active tab — check virtual_desk first; the first call per session is redirected to virtual_desk.switch_tabOpen a new tab, switch to a tab by ID (from virtual_desk), or close one. Prefer 'open' over navigate when the user's active tab must stay untouched. Refs from the previous tab are invalid afterwards — call view_page before acting.tab_statusActive tab's cached URL, title, ready state and errors — a cheap mid-workflow sanity check ('did my click navigate?'). Not for tab discovery or page content.wait_forWait until a condition holds: element visible, page text present, URL match, network idle, or a JS expression true. Prefer condition 'text' over a JS expression for 'has the page said X yet'. assert: true checks once and fails instead of waiting.- +13 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"
]
}
}
}
Public Browser
{
"mcpServers": {
"public-browser": {
"command": "npx",
"args": [
"-y",
"public-browser@latest"
]
}
}
}
Frequently asked questions
Camoufox MCP is categorized under Browser Automation and uses a local stdio subprocess. Public Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Camoufox MCP for browser automation work and Public 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.
Camoufox MCP has no declared pricing — check the project's own site. Public 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 camoufox-mcp and public-browser 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. Public Browser has 64/100 (Good) with 1 views, 0 installs and 19 GitHub stars.