Skip to content

Summary

Mozilla's official MCP server that lets AI agents drive Firefox for browsing tasks and inspect pages with its developer tools, over WebDriver BiDi.

Features

  • Agentic browsing: navigate, snapshot, click and fill pages
  • Developer tools: console, network requests, debugger and profiler
  • Tool presets from slim to all, or an explicit module list
  • Headless mode, attach to a running Firefox, or Firefox for Android over ADB
  • Official Mozilla project, MIT or Apache-2.0

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Firefox MCP" tools will be available.
{
  "mcpServers": {
    "firefox-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mozilla/firefox-mcp@latest",
        "--headless",
        "--viewport",
        "1280x720"
      ],
      "env": {
        "START_URL": "about:blank"
      }
    }
  }
}

Description

Firefox MCP is Mozilla's Model Context Protocol server for Firefox. It controls a local Firefox through WebDriver BiDi (via Selenium WebDriver) and covers two jobs: agentic browsing, where the agent reads pages, fills forms and works through multi-step flows, and agent-assisted web development, where it loads the page you are building and inspects it with the console, network requests, the debugger and the profiler.

Tools and presets

Tools such as navigate_page, take_snapshot, click_by_uid, fill_by_uid, list_network_requests, screenshot_page and list_console_messages are grouped into modules. Presets choose how much to expose: slim, basic (the default), developer, mozilla for privileged browser internals, or all; --tools picks modules explicitly. It can run headless, attach to an already-running Firefox, and drive Firefox for Android over ADB.

Requirements and safety

It needs Node.js 20.19 or later and Firefox 100+ installed locally, so it cannot run on cloud hosts. Mozilla recommends a dedicated Firefox profile, since the agent can reach anything the browser can, and notes that the default preset includes evaluate_script; slim drops it. The package moved to @mozilla/firefox-mcp and is still published as @mozilla/firefox-devtools-mcp for existing setups. Dual-licensed MIT or Apache-2.0.

Who it is for

Web developers and agent builders who want a Firefox counterpart to Chrome-based browser servers, from Claude Code, Codex, Claude Desktop, Cursor or Cline.

MCP: Chrome DevTools MCP

by Google Chrome DevTools team

Google's official MCP server for driving and inspecting a real Chrome browser — automation, debugging, and performance traces.

MCP: Playwright

by Microsoft

Browser automation for agents — navigate, click, type, and read pages using Playwright's accessibility tree, no screenshots required.

Browse all MCP servers →