Pixelcheck vs Firefox Devtools MCP

A side-by-side look at the Pixelcheck 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.

Pixelcheck logoPixelcheckBrowser Automation · Local subprocess (stdio)Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic.57GoodAuth: not declaredFirefox Devtools MCP logoFirefox Devtools MCPBrowser Automation · Local subprocess (stdio)Firefox browser automation via WebDriver BiDi for testing, scraping, and browser control. Supports snapshot/UID-based interactions, network monitoring, console capture, and screenshots.72GreatAuth: no auth required

Verdict: choose Pixelcheck 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?

Pixelcheck logoChoose Pixelcheck when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: ANTHROPIC_API_KEY.
  • You want tools like audit_url, explore_url, see.
Explore Pixelcheck

Firefox Devtools MCP logoChoose 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.
Explore Firefox Devtools MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPixelcheck logoPixelcheckFirefox Devtools MCP logoFirefox Devtools MCP
CategoryBrowser AutomationBrowser Automation
Quality signal57/100 · Good72/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsANTHROPIC_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars6516
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools1234

Tools & capabilities

Pixelcheck tools 12

  • audit_urlYou want the full audit pipeline against one URL — agent loop, scoring, JSON + HTML report.
  • explore_urlYou want a quick autonomous run with a free-form goal; no scenario YAML needed.
  • seeYou want to look at a URL once and get back DOM summary + screenshot + console errors + an optional natural-language note. 0 LLM cost when `goal` is omitted.
  • actYou want to drive an action sequence (click / fill / scroll / screenshot / natural-language `act` / vision `note`) and get back per-step status + final DOM + screenshot.
  • extractYou want a typed payload back from a URL — pricing tiers, feature lists, FAQ entries — shaped exactly the way you asked for. Hand the tool a JSON Schema; get back `data` matching it plus DOM / console / screenshot.
  • judgeYou want a rubric-driven critique of one URL — aesthetic polish, dark-pattern risk, or any custom rubric. Returns per-criterion scores (0..10) + severity-graded findings with on-screen locations. 1 vision call.
  • compareYou want an A/B comparison of two URLs against the same rubric. Default `double_blind` mode judges each side independently then synthesises a comparison (3 vision calls, free of anchoring bias). `fast` mode is 1 call (cheaper, anchored).
  • list_personasDiscover which personas are installed in a project.
  • list_scenariosDiscover which scenarios are installed in a project.
  • list_capabilitiesSelf-describe the server: every shipped tool with kind / cacheability / static cost band / side-effects / dependency declarations, plus the public env-var table and live result-cache state. Pure introspection — call it once on first connect to plan the rest of your session.
  • calibrate_criticRun the critic calibration gate against labeled fixtures (returns pass/fail + agreement metrics).
  • get_last_reportRead the most recent audit's summary JSON from the local history DB.

Firefox Devtools MCP tools 34

  • 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.
  • +22 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.

Pixelcheck

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pixelcheck": {
      "command": "npx",
      "args": [
        "-y",
        "pixelcheck"
      ],
      "env": {
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE"
      }
    }
  }
}

Firefox Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "freema-firefox-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mozilla/firefox-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Pixelcheck 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 Pixelcheck 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.

Pixelcheck has no declared pricing — check the project's own site. 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 pixelcheck and freema-firefox-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Pixelcheck has a quality signal of 57/100 (Good) with 0 views, 0 installs and 6 GitHub stars. Firefox Devtools MCP has 72/100 (Great) with 6 views, 0 installs and 516 GitHub stars.