接入你的智能体
发布者自己的命令。不是 PlugMCP 端点。
用我们的密钥与日志托管一份副本。
npx -y @mozilla/[email protected]Claude Code 没有针对本地命令的安装链接。复制下方命令并在终端中运行。
claude mcp add mozilla-firefox-devtools-mcp-moz -- npx -y @mozilla/firefox-devtools-mcp-moz@0.10.7在终端中运行。
{ "mcpServers": { "mozilla-firefox-devtools-mcp-moz": { "command": "npx", "args": [ "-y", "@mozilla/[email protected]" ] } }}claude_desktop_config.json
远程 URL 还是本机命令？ 两种安装方式的区别
Model Context Protocol server that lets AI agents use Firefox. It has two main use cases:
It controls Firefox through WebDriver BiDi (via Selenium WebDriver) and works with Claude Code, Claude Desktop, Cursor, Cline and other MCP clients.
Repository: https://github.com/mozilla/firefox-devtools-mcp
Note: This MCP server requires a local Firefox browser installation and cannot run on cloud hosting services like glama.ai. Use
npx @mozilla/firefox-devtools-mcp@latestto run locally, or use Docker with the provided Dockerfile.
Browser MCP servers carry inherent risks. A few key practices:
basic preset already includes evaluate_script; --tool-preset slim drops it. Higher presets such as --tool-preset developer (debugging, network, console, profiler) and --tool-preset mozilla (privileged context) expand what the agent can do further.See SECURITY.md for a full breakdown of risks and how to report vulnerabilities.
--firefox-path)Recommended: use npx so you run the latest published version from npm.
claude mcp add firefox-devtools npx @mozilla/firefox-devtools-mcp@latest
# Headless + viewport via args
claude mcp add firefox-devtools npx @mozilla/firefox-devtools-mcp@latest -- --headless --viewport 1280x720
# Or via environment variables
claude mcp add firefox-devtools npx @mozilla/firefox-devtools-mcp@latest \
--env START_URL=https://example.com \
--env FIREFOX_HEADLESS=true
codex mcp add firefox-devtools -- npx @mozilla/firefox-devtools-mcp@latest
# Headless + viewport via args
codex mcp add firefox-devtools -- \
npx @mozilla/firefox-devtools-mcp@latest -- --headless --viewport 1280x720
# Or via environment variables
codex mcp add firefox-devtools \
--env START_URL=https://example.com \
--env FIREFOX_HEADLESS=true \
-- npx @mozilla/firefox-devtools-mcp@latest
Add to Claude Code’s mcp_settings.json:
{
"mcpServers": {
"firefox-devtools": {
"command": "npx",
"args": ["-y", "@mozilla/firefox-devtools-mcp@latest", "--headless", "--viewport", "1280x720"],
"env": {
"START_URL": "about:blank"
}
}
}
}
Add to ~/.codex/config.toml:
[mcp_servers.firefox-devtools]
command = "npx"
args = ["-y", "@mozilla/firefox-devtools-mcp@latest", "--headless", "--viewport", "1280x720"]
[mcp_servers.firefox-devtools.env]
START_URL = "about:blank"
npm run setup
# Choose Claude Code; the script saves JSON to the right path
npx @modelcontextprotocol/inspector npx @mozilla/firefox-devtools-mcp@latest --start-url https://example.com --headless
Then call tools like:
list_pages, select_page, navigate_pagetake_snapshot then click_by_uid / fill_by_uidlist_network_requests (always‑on capture), get_network_requestlist_downloads (always‑on capture), set_download_behaviorscreenshot_page, list_console_messagesYou can pass flags or environment variables (names on the right):
--firefox-path — absolute path to Firefox binary--headless — run without UI (FIREFOX_HEADLESS=true)--viewport 1280x720 — initial window size--profile-path — use a specific Firefox profile. Firefox runs in a firefox_devtools_mcp_profile subfolder of that path, marked with a .firefox-devtools-mcp file; pointing --profile-path at a marked profile reuses it directly--firefox-arg — extra Firefox arguments (repeatable)--start-url — open this URL on start (START_URL)--accept-insecure-certs — ignore TLS errors (ACCEPT_INSECURE_CERTS=true)--connect-existing — attach to an already-running Firefox instead of launching a new one (CONNECT_EXISTING=true)--marionette-port — Marionette port for connect-existing mode, default 2828 (MARIONETTE_PORT)--idle-timeout — seconds without tool calls after which a connect-existing session releases Firefox, default 1800. Firefox accepts one client at a time, so other clients can only connect once it is released. The next tool call reconnects and selects the tab that is active in Firefox at that moment (IDLE_TIMEOUT)--pref name=value — set Firefox preference at startup via moz:firefoxOptions (repeatable)--tool-preset — select which tool modules to enable: slim, basic (default), developer, mozilla, or all. See Tool modules and presets. (TOOL_PRESET)--tools — explicit list of tool modules to enable, overriding --tool-preset entirely (e.g. --tools pages network script). See Tool modules and presets.--enable-script — deprecated, use --tool-preset developer or --tools ... script debugging. Selects the developer tool preset. (ENABLE_SCRIPT=true)--enable-privileged-context — deprecated, use --tool-preset mozilla or --tools ... privileged prefs. Selects the mozilla tool preset. Requires MOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1 (ENABLE_PRIVILEGED_CONTEXT=true)--android-device — enable Firefox for Android mode; value is the ADB device serial (e.g. emulator-5554). Run adb devices to list connected devices. Omit the value or use auto to select the single connected device automatically.--android-wipe-app-data — confirm that Android mode wipes all data of the target app. Required together with --android-device. (ANDROID_WIPE_APP_DATA=true)--android-package — Android app package name, default org.mozilla.firefox. Other packages: org.mozilla.firefox_beta for Firefox Beta, org.mozilla.fenix for Firefox Nightly, org.mozilla.fenix.debug for Firefox Nightly Debug, org.mozilla.geckoview_example for geckoview (ANDROID_PACKAGE)--unrestricted-save-paths — let the saveTo parameter write anywhere on disk instead of the default roots. See Saving bulky output to disk and the security note in SECURITY.md. (UNRESTRICTED_SAVE_PATHS=true)--log-file — write MCP server logs to a file instead of stderr. Useful for debugging sessions with MCP clients that hide server output. Set DEBUG=* to also include verbose debug logs. Example: --log-file /tmp/firefox-mcp.logTools are grouped into modules. You choose which modules to expose either with a named preset
(--tool-preset) or with an explicit list (--tools). When both are given, --tools wins and
the preset is ignored.
Presets (each is a superset of the previous):
slim — the minimum to browse and interact with pagesbasic (default) — adds tools for regular browsingdeveloper — adds tools for web developersmozilla — adds tools for Firefox developersall — every moduleSee docs/tools.md for the list of modules and the modules in each preset.
Note that basic, the default, includes script and therefore the evaluate_script tool.
See SECURITY.md for what that means for the attack
surface, and use --tool-preset slim or an explicit --tools list to drop it.
# Use the developer preset (adds network, console, debugging and profiler tools)
npx @mozilla/firefox-devtools-mcp --tool-preset developer
# Enable only the modules you need
npx @mozilla/firefox-devtools-mcp --tools pages network console
The prefs and privileged modules require MOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1 and are only
available in the Mozilla-internal build. The launch module requires the Mozilla-internal
build too: it restarts Firefox under a caller-chosen binary, profile, environment and set of
preferences, which is a configuration change the operator should own. Use --pref,
--firefox-path and the other command-line options instead. The bidi module also requires
the Mozilla-internal build: it sends any WebDriver BiDi command, so it gives access to what the
other modules expose. The public package skips these modules even if requested and logs a
warning naming the modules it dropped.
--pref)Use --android-device to automate Firefox running on an Android device. Requires adb on your PATH and geckodriver, which is managed automatically.
Warning: Android mode wipes all data of the target app before every session. Tabs, history, bookmarks, passwords, cookies and settings are all lost. geckodriver runs
adb shell pm clear <package>when creating the session and offers no way to skip it, then runs the session on its own temporary profile which is deleted afterwards. Because of this,--android-devicerequires--android-wipe-app-data, and you should install a build dedicated to automation rather than automating the browser you use. Bug 2064088 tracks adding an option to geckodriver to keep the existing app data.
# List connected devices
adb devices
# Launch Firefox for Android on the single connected device
npx @mozilla/firefox-devtools-mcp --android-device auto --android-wipe-app-data
# Target a specific device
npx @mozilla/firefox-devtools-mcp --android-device <serial> --android-wipe-app-data
# Use Firefox Nightly instead
npx @mozilla/firefox-devtools-mcp --android-device <serial> --android-package org.mozilla.fenix --android-wipe-app-data
Port forwarding between the host and device is handled automatically by geckodriver.
Use --connect-existing to automate your real browsing session, with cookies, logins, and open tabs intact:
# Start Firefox with Marionette and the Remote Agent (BiDi)
firefox --marionette --remote-debugging-port
# Run the MCP server
npx @mozilla/firefox-devtools-mcp --connect-existing --marionette-port 2828
Both flags are required because the MCP uses both WebDriver Classic (--marionette) and WebDriver BiDi (--remote-debugging-port). If Firefox is only started with --marionette, the MCP server fails to connect and asks you to restart Firefox with both flags.
If Firefox is already running with the same profile, the command above only opens a new window in that instance: the flags are ignored, so neither Marionette nor the Remote Agent starts.
To keep your everyday Firefox running without Marionette, give the MCP server its own profile. Firefox runs one process per profile, so both instances run side by side, and the agent only reaches what you sign in to in that profile:
# Once: create a dedicated profile
firefox -CreateProfile firefox-mcp
# Start it with Marionette and the Remote Agent, next to your everyday Firefox
firefox -P firefox-mcp --marionette --remote-debugging-port
Warning: Do not leave Marionette enabled during normal browsing. It sets
navigator.webdriver = trueand changes other browser fingerprint signals, which can trigger bot detection on sites protected by Cloudflare, Akamai, etc. Only enable Marionette when you need MCP automation, then restart Firefox normally afterward, or run it in a dedicated profile as shown above.
See docs/tools.md for the full list of tools by module, with descriptions and parameters (generated from the source).
Large tool output can consume significant context in CLI clients like Claude Code. Several
tools accept an optional saveTo parameter that writes the result to a file instead of
returning it inline. See docs/tools.md for the list.
saveTo takes one of three forms:
~/.firefox-devtools-mcp/output; parent directories are created). Paths reaching a Firefox profile, or the files this server reads back, are refusedtrue (a timestamped file is generated under ~/.firefox-devtools-mcp/output/)The response returns the path and byte size. The saved file always holds the full, untruncated data: the inline size safeguards (console message caps, network header truncation, snapshot line caps) never apply to it.
The text-producing tools also accept preview, a number of characters of the saved output to
echo back inline as a short excerpt. The list in docs/tools.md shows which tools support it.
screenshot_page({ saveTo: "page.png" })
take_snapshot({ saveTo: true })
list_network_requests({ urlContains: "api", saveTo: "network.json" })
evaluate_script({ function: "() => performance.getEntries()", saveTo: true, preview: 2000 })
By default, save paths are restricted: relative paths resolve against the current working
directory, and absolute paths are only allowed within ~/.firefox-devtools-mcp. Paths that
escape these locations are rejected. Start the server with --unrestricted-save-paths to
write to arbitrary locations, including absolute paths outside that directory.
Saved files can then be viewed for instance with Claude Code's Read tool without impacting context size.
npm install
npm run build
# Run with Inspector against local build
npx @modelcontextprotocol/inspector node dist/index.js --headless --viewport 1280x720
# Or run in dev with hot reload
npm run inspector:dev
See CONTRIBUTING.md for more details on local development, testing, and CI.
--firefox-path "/Applications/Firefox.app/Contents/MacOS/firefox" (macOS) or the correct path on your OS.take_snapshot) when a UID tool reports one is gone.Solution 1 Wrap with cmd /c (details):
"mcpServers": {
"firefox-devtools": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@mozilla/firefox-devtools-mcp@latest"]
}
}
Solution 2 Use the absolute path to npx (adjust extension — .cmd, .bat, .exe, or .ps1 — to match your setup):
"mcpServers": {
"firefox-devtools": {
"command": "C:\\nvm4w\\nodejs\\npx.ps1",
"args": ["-y", "@mozilla/firefox-devtools-mcp@latest"]
}
}
0.x. Use @latest with npx for the newest release.See CONTRIBUTING.md for how to file issues, run tests, and work on the project locally.
Maintained by Mozilla.
Licensed under either of MIT or Apache 2.0 at your option.
Model Context Protocol (MCP) server that lets AI agents browse the web and debug web pages with Firefox (moz build with privileged context support)
{ "mcpServers": { "mozilla-firefox-devtools-mcp-moz": { "command": "npx", "args": [ "-y", "@mozilla/[email protected]" ] } }}工具
暂无工具列表。远程服务器在首次健康检查后会获得工具列表。
常见问题
在本页复制适用于 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 配置。它使用发布者的安装方式，而不是 PlugMCP 代理。
此记录未列出必需的环境变量。
@mozilla/firefox Devtools MCP Moz 通过 stdio 在本地运行。
上次检查时间：2026-11-14。 Model Context Protocol (MCP) server that lets AI agents browse the web and debug web pages with Firefox (moz build with privileged context support)