AI agent이 웹사이트를 탐색하고 콘솔, 네트워크, 디버거, 프로파일러와 같은 개발자 도구를 사용하여 Firefox 페이지를 검사할 수 있습니다.
다른 이름 mozilla/firefox-devtools-mcp, firefox-devtools-mcp, @mozilla/firefox-devtools-mcp
- 스타
- 571
- Tools
- 35
- 다운로드, 30일
- —
- 최신 버전
- 0.10.7
- 마지막 커밋
- 2026년 11월 4일
- 라이선스
- —
Firefox DevTools MCP란?
AI agent이 웹사이트를 탐색하고 콘솔, 네트워크, 디버거, 프로파일러와 같은 개발자 도구를 사용하여 Firefox 페이지를 검사할 수 있습니다. 35개 도구를 제공합니다. 예: list_pages, new_page, navigate_page.
프로젝트 README에서 생성된 요약
Firefox DevTools MCP server 정보
웹 개발자와 자동화된 agent는 이 MCP server를 통해 로컬 Firefox 브라우저를 제어함으로써 실제 웹사이트와 상호작용할 수 있습니다. 양식 작성이나 다단계 웹사이트 흐름 탐색과 같은 agentic browsing 작업을 가능하게 하며, 웹 개발을 위한 심층 검사 기능도 제공합니다. WebDriver BiDi를 사용하여 AI 클라이언트가 콘솔, 네트워크 모니터, 디버거, 프로파일러를 포함한 전문 디버깅 도구에 접근할 수 있도록 합니다.
사용자는 npx 또는 Docker를 사용하여 이 server를 로컬에서 실행할 수 있으며, Claude Desktop, Claude Code, Cursor, Cline과 같은 클라이언트와 호환됩니다. 보안 및 기능을 관리하기 위해 slim, basic, developer 또는 mozilla와 같은 다양한 도구 프리셋을 선택할 수 있습니다. 또한 ADB를 통해 Android 기기에서 Firefox를 자동화하는 기능도 지원합니다. 실제 브라우저와 상호작용하므로 개인 쿠키와 저장된 세션을 보호하기 위해 전용 Firefox 프로필을 사용하는 것을 권장합니다.
활용 사례
- 1자동 웹 탐색AI agent가 콘텐츠 읽기나 다단계 사용자 흐름 완료와 같은 일상적인 웹사이트 작업을 수행할 수 있습니다.
- 2웹 개발 디버깅개발자는 AI가 전문 개발자 도구를 사용하여 실제 페이지를 검사하고 문제를 해결하도록 할 수 있습니다.
- 3모바일 브라우저 자동화ADB와 특정 패키지 설정을 사용하여 Android 기기에서 실행되는 Firefox를 자동화할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Firefox DevTools MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Firefox DevTools MCP 설치
$ claude mcp add firefox-devtools-mcp -- npx -y @mozilla/firefox-devtools-mcpCursor에 Firefox DevTools MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"firefox-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp"
]
}
}
}VS Code에 Firefox DevTools MCP 설치
.vscode/mcp.json
{
"servers": {
"firefox-devtools-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp"
]
}
}
}VS Code CLI에 Firefox DevTools MCP 설치
$ code --add-mcp '{"name":"firefox-devtools-mcp","type":"stdio","command":"npx","args":["-y","@mozilla/firefox-devtools-mcp"]}'Claude Desktop에 Firefox DevTools MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"firefox-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp"
]
}
}
}Codex에 Firefox DevTools MCP 설치
$ codex mcp add firefox-devtools-mcp -- npx -y @mozilla/firefox-devtools-mcpCodex config.toml에 Firefox DevTools MCP 설치
~/.codex/config.toml
[mcp_servers.firefox-devtools-mcp] command = "npx" args = ["-y", "@mozilla/firefox-devtools-mcp"]
Gemini CLI에 Firefox DevTools MCP 설치
$ gemini mcp add -s user firefox-devtools-mcp npx -- -y @mozilla/firefox-devtools-mcpGemini settings.json에 Firefox DevTools MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"firefox-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp"
]
}
}
}HostedMCP가 2026년 11월 16일에 실행 확인
@mozilla/firefox-devtools-mcp 0.10.7을(를) 네트워크와 키가 없는 격리된 컨테이너에서 이 명령으로 실행했습니다. 응답하며 도구 35개를 보여 주었습니다.
Firefox DevTools MCP 도구 35
tools/list로 서버에서 직접 읽음list_pages읽기 전용List open tabs (index, title, URL). Selected tab is marked.
new_page작업Open new tab at URL. Returns tab index.
navigate_page작업Navigate selected tab to URL.
select_page작업Select active tab by index, URL, or title. Index takes precedence.
close_page작업Close tab by index.
get_page_text읽기 전용Get the visible text of the page (document.body.innerText). Caps at maxLength (default 20000 chars); saveTo saves the full text to a file.
take_snapshot읽기 전용Capture 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_selector읽기 전용Resolve UID to CSS selector. Fails if the element is gone.
clear_snapshot작업Clear snapshot UIDs. Usually not needed.
click_by_uid작업Click element by UID. Set dblClick for double-click.
hover_by_uid작업Hover over element by UID.
fill_by_uid작업Fill text input/textarea by UID.
| list_pages | List open tabs (index, title, URL). Selected tab is marked. | 읽기 전용 |
| new_page | Open new tab at URL. Returns tab index. | 작업 |
| navigate_page | Navigate selected tab to URL. | 작업 |
| select_page | Select active tab by index, URL, or title. Index takes precedence. | 작업 |
| close_page | Close tab by index. | 작업 |
| get_page_text | Get the visible text of the page (document.body.innerText). Caps at maxLength (default 20000 chars); saveTo saves the full text to a file. | 읽기 전용 |
| take_snapshot | Capture 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_selector | Resolve UID to CSS selector. Fails if the element is gone. | 읽기 전용 |
| clear_snapshot | Clear snapshot UIDs. Usually not needed. | 작업 |
| click_by_uid | Click element by UID. Set dblClick for double-click. | 작업 |
| hover_by_uid | Hover over element by UID. | 작업 |
| fill_by_uid | Fill text input/textarea by UID. | 작업 |
도구 35개 모두 보기도구 수 줄이기
drag_by_uid_to_uid작업Drag element to another (HTML5 drag events).
fill_form_by_uid작업Fill multiple form fields at once.
upload_file_by_uid작업Upload file to file input by UID.
press_key작업Press a single key, optionally with modifiers, to submit, dismiss, navigate or trigger a shortcut. Not for entering text: use fill_by_uid instead.
type_text작업Type text key by key into the focused element, optionally followed by a key such as Enter. Use fill_by_uid to set the value of a known input; use this for elements that only react to real typing, such as autocomplete fields and rich text editors.
screenshot_page읽기 전용Capture viewport screenshot as base64 PNG. Set fullPage for the whole scrollable document.
screenshot_by_uid읽기 전용Capture element screenshot by UID as base64 PNG.
print_page읽기 전용Print the current page to a PDF file using print CSS. Returns the saved file path.
list_downloads읽기 전용List downloads tracked since startup, including status and saved file path.
clear_downloadsClear the tracked downloads buffer.
set_download_behaviorControl how downloads are handled: allow (save to a destination folder), deny (cancel), or reset to default. Avoids the native save-file dialog. Requires a recent Firefox.
accept_dialog작업Accept browser dialog. Provide promptText for prompts.
dismiss_dialog작업Dismiss browser dialog.
navigate_history작업Navigate history back/forward. UIDs become stale.
set_viewport_size작업Set viewport dimensions in pixels. Applies to the selected tab only.
get_firefox_output읽기 전용Retrieve Firefox output (stdout/stderr including MOZ_LOG, warnings, crashes, stack traces). Returns recent output from the capture file. Use filters to focus on specific content.
get_firefox_info읽기 전용Get information about the current Firefox instance configuration, including binary path, environment variables, and output file location.
close_firefox_session작업Ends the browser session. If the server connected to your existing Firefox, this releases the connection and leaves Firefox running. If the server started Firefox itself, this closes it. Call this when the browser task is complete and no further browser interaction is expected.
install_extension작업Install a Firefox extension using WebDriver BiDi webExtension.install command. Supports installing from archive (.xpi/.zip), base64-encoded data, or unpacked directory.
uninstall_extension작업Uninstall a Firefox extension using WebDriver BiDi webExtension.uninstall command. Requires the extension ID returned by install_extension or obtained from list_extensions.
screencast_start작업Start recording a screencast (video) of the current page viewport, saving the output to a file in the downloads directory. Returns a screencast id to pass to screencast_stop. Multiple recordings can run at once.
screencast_stop작업Stop an in-progress screencast recording started with screencast_start and finalize the video file. Returns the path to the saved file.
evaluate_script작업Run a JS function in the page and return its result. Prefer this for targeted reads (a value, text, computed style, whether an element exists) instead of a full take_snapshot. Use the UID interaction tools for clicking, typing, and filling.
| drag_by_uid_to_uid | Drag element to another (HTML5 drag events). | 작업 |
| fill_form_by_uid | Fill multiple form fields at once. | 작업 |
| upload_file_by_uid | Upload file to file input by UID. | 작업 |
| press_key | Press a single key, optionally with modifiers, to submit, dismiss, navigate or trigger a shortcut. Not for entering text: use fill_by_uid instead. | 작업 |
| type_text | Type text key by key into the focused element, optionally followed by a key such as Enter. Use fill_by_uid to set the value of a known input; use this for elements that only react to real typing, such as autocomplete fields and rich text editors. | 작업 |
| screenshot_page | Capture viewport screenshot as base64 PNG. Set fullPage for the whole scrollable document. | 읽기 전용 |
| screenshot_by_uid | Capture element screenshot by UID as base64 PNG. | 읽기 전용 |
| print_page | Print the current page to a PDF file using print CSS. Returns the saved file path. | 읽기 전용 |
| list_downloads | List downloads tracked since startup, including status and saved file path. | 읽기 전용 |
| clear_downloads | Clear the tracked downloads buffer. | |
| set_download_behavior | Control how downloads are handled: allow (save to a destination folder), deny (cancel), or reset to default. Avoids the native save-file dialog. Requires a recent Firefox. | |
| accept_dialog | Accept browser dialog. Provide promptText for prompts. | 작업 |
| dismiss_dialog | Dismiss browser dialog. | 작업 |
| navigate_history | Navigate history back/forward. UIDs become stale. | 작업 |
| set_viewport_size | Set viewport dimensions in pixels. Applies to the selected tab only. | 작업 |
| get_firefox_output | Retrieve Firefox output (stdout/stderr including MOZ_LOG, warnings, crashes, stack traces). Returns recent output from the capture file. Use filters to focus on specific content. | 읽기 전용 |
| get_firefox_info | Get information about the current Firefox instance configuration, including binary path, environment variables, and output file location. | 읽기 전용 |
| close_firefox_session | Ends the browser session. If the server connected to your existing Firefox, this releases the connection and leaves Firefox running. If the server started Firefox itself, this closes it. Call this when the browser task is complete and no further browser interaction is expected. | 작업 |
| install_extension | Install a Firefox extension using WebDriver BiDi webExtension.install command. Supports installing from archive (.xpi/.zip), base64-encoded data, or unpacked directory. | 작업 |
| uninstall_extension | Uninstall a Firefox extension using WebDriver BiDi webExtension.uninstall command. Requires the extension ID returned by install_extension or obtained from list_extensions. | 작업 |
| screencast_start | Start recording a screencast (video) of the current page viewport, saving the output to a file in the downloads directory. Returns a screencast id to pass to screencast_stop. Multiple recordings can run at once. | 작업 |
| screencast_stop | Stop an in-progress screencast recording started with screencast_start and finalize the video file. Returns the path to the saved file. | 작업 |
| evaluate_script | Run a JS function in the page and return its result. Prefer this for targeted reads (a value, text, computed style, whether an element exists) instead of a full take_snapshot. Use the UID interaction tools for clicking, typing, and filling. | 작업 |
구성
FIREFOX_HEADLESSSet to true to run Firefox without a visible window.
START_URLSTART_URLURL to open when the server starts.
| 이름 | 설명 | 유형 |
|---|---|---|
| FIREFOX_HEADLESS | Set to true to run Firefox without a visible window. | |
| START_URL | — | |
| START_URL | URL to open when the server starts. |
자동 검사
2026년 11월 16일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능mozilla/firefox-devtools-mcp is public and reachablegithub.com/mozilla/firefox-devtools-mcp ↗통과
- 패키지가 이 저장소를 소스로 명시@mozilla/firefox-devtools-mcp names mozilla/firefox-devtools-mcp as sourcenpmjs.com/package/@mozilla/firefox-devtools-mcp ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @mozilla/firefox-devtools-mcpnpmjs.com/package/@mozilla/firefox-devtools-mcp/v/0.10.7#pro ↗통과
- 오픈 소스 라이선스 (OSI)No license결함 발견
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-04github.com/mozilla/firefox-devtools-mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @mozilla/firefox-devtools-mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음150 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음35 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Firefox DevTools MCP
Model Context Protocol server that lets AI agents use Firefox. It has two main use cases:
- Agentic browsing: the agent uses the browser for regular tasks, such as reading pages, filling forms and going through multi-step flows on websites.
- Agent-assisted web development: the agent loads the page you are working on and inspects it with developer tools, such as the console, network requests, the debugger and the profiler.
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.
Security
Browser MCP servers carry inherent risks. A few key practices:
- Use a dedicated Firefox profile. Never run the server against your regular profile — the agent has access to whatever the browser can reach, including cookies and saved sessions.
- Be cautious about which sites you visit. Pages can return content designed to manipulate the agent (prompt injection). Stick to sites you control or trust.
- Enable only the tool modules you need. The default
basicpreset already includesevaluate_script;--tool-preset slimdrops 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.
Requirements
- Node.js ≥ 20.19.0
- Firefox 100+ installed (auto‑detected, or pass
--firefox-path)
Install and use with Claude Code or Codex (npx)
Recommended: use npx so you run the latest published version from npm.
Option A — CLI
Claude Code
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
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
Option B — Edit the configuration file
Claude Code
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"
}
}
}
}
Codex
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"
Option C — Helper script (local dev build)
npm run setup
# Choose Claude Code; the script saves JSON to the right path
Try it with MCP Inspector
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_snapshotthenclick_by_uid/fill_by_uidlist_network_requests(always‑on capture),get_network_requestlist_downloads(always‑on capture),set_download_behaviorscreenshot_page,list_console_messages
CLI options
You 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 afirefox_mcp_profilesubfolder of that path, marked with a.firefox-mcpfile; pointing--profile-pathat 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 viamoz:firefoxOptions(repeatable)--tool-preset— select which tool modules to enable:slim,basic(default),developer,mozilla, orall. See Tool modules and presets. (TOOL_PRESET)--tools— explicit list of tool modules to enable, overriding--tool-presetentirely (e.g.--tools pages network script). See Tool modules and presets.--enable-script— deprecated, use--tool-preset developeror--tools ... script debugging. Selects thedevelopertool preset. (ENABLE_SCRIPT=true)--enable-privileged-context— deprecated, use--tool-preset mozillaor--tools ... privileged prefs. Selects themozillatool preset. RequiresMOZ_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). Runadb devicesto list connected devices. Omit the value or useautoto 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, defaultorg.mozilla.firefox. Other packages:org.mozilla.firefox_betafor Firefox Beta,org.mozilla.fenixfor Firefox Nightly,org.mozilla.fenix.debugfor Firefox Nightly Debug,org.mozilla.geckoview_examplefor geckoview (ANDROID_PACKAGE)--unrestricted-save-paths— let thesaveToparameter 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. SetDEBUG=*to also include verbose debug logs. Example:--log-file /tmp/firefox-mcp.log
Tool modules and presets
Tools 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 module
See 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.
Useful preferences (--pref)
- remote.prefs.recommended=false. When Firefox runs in automation, it applies RecommendedPreferences that modify browser behavior for testing. Set remote.prefs.recommended to false to skip those and have a configuration closer to a regular Firefox instance.
- remote.log.level=Trace. Enable verbose WebDriver protocol logs in Firefox. The MCP server will automatically pass the matching log level to geckodriver so both sides log at the same verbosity.
- app.update.disabledForTesting=false. Allow Firefox to automatically download and apply updates. Note that updates may interrupt your session. Requires also setting remote.prefs.recommended=false.
Firefox for Android
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.
Connect to existing Firefox
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.
Tool overview
See docs/tools.md for the full list of tools by module, with descriptions and parameters (generated from the source).
Saving bulky output to disk
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:
- a file path (relative to the current working directory, or absolute within
~/.firefox-mcp/output; parent directories are created). Paths reaching a Firefox profile, or the files this server reads back, are refused - an existing directory (a timestamped file is generated inside it)
true(a timestamped file is generated under~/.firefox-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-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.
Local development
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.
Troubleshooting
- Firefox not found: pass
--firefox-path "/Applications/Firefox.app/Contents/MacOS/firefox"(macOS) or the correct path on your OS. - First run is slow: Selenium sets up the BiDi session; subsequent runs are faster.
- Stale UIDs: a UID stays valid until its element is removed or the page navigates; take a fresh snapshot (
take_snapshot) when a UID tool reports one is gone. - Windows 10: Error during discovery for MCP server 'firefox-devtools': MCP error -32000: Connection closed
-
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"] } }
-
Versioning
- Pre‑1.0 API: versions start at
0.x. Use@latestwith npx for the newest release.
Contributing
See CONTRIBUTING.md for how to file issues, run tests, and work on the project locally.
Author
Maintained by Mozilla.
License
Licensed under either of MIT or Apache 2.0 at your option.
Firefox DevTools MCP 질문
Firefox DevTools MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add firefox-devtools-mcp -- npx -y @mozilla/firefox-devtools-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Firefox DevTools MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Firefox DevTools MCP는 어떤 도구를 제공하나요?
35개 도구를 제공합니다. 예: list_pages, new_page, navigate_page, select_page, close_page.
Firefox DevTools MCP를 사용하려면 로컬에 Firefox가 설치되어 있어야 하나요?
네. 이 MCP server는 로컬 Firefox 브라우저를 실행하거나 연결하여 작동하므로 클라우드 호스팅 서비스에서는 실행할 수 없습니다.
Claude Code에서 Firefox DevTools MCP를 어떻게 설치하나요?
claude mcp add 명령어를 사용하여 @mozilla/firefox-devtools-mcp 패키지를 npx로 추가하면 됩니다.
새 브라우저를 실행하는 대신 이미 실행 중인 Firefox에 연결할 수 있나요?
네, --connect-existing 플래그(또는 CONNECT_EXISTING=true)를 전달하면 실행 중인 Firefox에 연결할 수 있습니다. Marionette 포트 기본값은 2828입니다.
어떤 도구 프리셋을 사용할 수 있나요?
slim, basic(기본값), developer, mozilla, all 프리셋이 있으며, 각 프리셋은 이전 프리셋의 기능을 포함하는 상위 집합입니다. 또한 --tools를 통해 모듈을 직접 선택할 수 있습니다.
Android의 Firefox를 자동화할 수 있나요?
네, --android-device와 --android-wipe-app-data를 사용하여 가능하지만, 매 세션마다 모든 앱 데이터를 삭제하며 adb가 필요합니다.