Firefox Devtools MCP vs MCP Server

A side-by-side look at the Firefox Devtools MCP and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Firefox 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 requiredMCP Server logoMCP ServerBrowser AutomationBrowserStack's Official MCP Server59GoodAuth: not declared

Verdict: choose Firefox Devtools MCP for browser automation work as a local process; choose MCP Server for browser automation. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

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

MCP Server logoChoose MCP Server when

  • You need dedicated capabilities in the Browser Automation domain.
  • You want tools like accessibilityExpert, startAccessibilityScan, createAccessibilityAuthConfig.
Explore MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFirefox Devtools MCP logoFirefox Devtools MCPMCP Server logoMCP Server
CategoryBrowser AutomationBrowser Automation
Quality signal72/100 · Great59/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars516155
Directory activity 6 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools3452

Tools & capabilities

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

MCP Server tools 52

  • accessibilityExpertAnswer accessibility, a11y, and WCAG questions using BrowserStack's accessibility knowledge base.
  • startAccessibilityScanStart an accessibility scan via BrowserStack and retrieve a local CSV report path.
  • createAccessibilityAuthConfigCreate an authentication configuration for accessibility scans. Supports both form-based and basic authentication.
  • getAccessibilityAuthConfigRetrieve an existing authentication configuration by ID. Requires the numeric id returned by createAccessibilityAuthConfig. No tool here lists existing configurations, so if you do not have the id, create one rather than guessing.
  • fetchAccessibilityIssuesFetch accessibility issues from a completed scan with pagination support. Use cursor parameter to get subsequent pages of results. Requires the ids of a completed scan, which are returned by startAccessibilityScan. No tool here lists past scans, so if you do not have the ids, start a new scan rather than guessing.
  • setupBrowserStackAutomateTestsSet up and run automated web-based tests on BrowserStack using the BrowserStack SDK. Use this tool for functional or integration test setup on BrowserStack only. For any visual testing or Percy integration, use the dedicated Percy setup tool. Example prompts: run this test on browserstack; set up this project for browserstack.
  • percyVisualTestIntegrationAgentIntegrate Percy visual testing into new projects and demonstrate visual change detection through a step-by-step simulation. This tool handles initial Percy integration, setup, and creates a working demonstration for new users. Primary tool for prompts like: "Integrate percy for this project", "Integrate percy in this project {project_name}"
  • expandPercyVisualTestingSet up or expand Percy visual testing configuration with comprehensive coverage for existing projects that might have Percy integrated. This supports both Percy Web Standalone and Percy Automate. Example prompts: Expand percy coverage for this project {project_name}
  • addPercySnapshotCommandsAdds Percy snapshot commands to the specified test files.
  • listTestFilesLists all test files for a given set of directories.
  • runPercyScanRun a Percy visual test scan. Example prompts : Run this Percy build/scan. Never run percy scan/build without this tool
  • fetchPercyChangesRetrieves and summarizes all visual changes detected by Percy AI between the latest and previous builds, helping quickly review what has changed in your project.
  • +40 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.

Firefox Devtools MCP

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

MCP Server

No confirmed install command for MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Firefox Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. MCP Server belongs to Browser Automation and uses an install path we have not confirmed yet. Pick Firefox Devtools MCP for browser automation work and MCP Server 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 Server has no confirmed install command yet — follow its own setup instructions.

Firefox Devtools MCP is listed as free. Auth: no auth required. MCP Server 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 freema-firefox-devtools-mcp and mcp-server-105 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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