Review · AISource: Mozilla
Firefox DevTools MCP 0.10.6 adds PDF output and fixes tab targeting
Mozilla’s Firefox DevTools MCP connects agents to Firefox for browser inspection; its documentation says the developer preset adds debugging, network, console and profiler tools. [1] The locally run server uses WebDriver BiDi via Selenium. [1] Mozilla lists Node 20.19.0+, Firefox 100+ and clients including Claude Code, Claude Desktop, Cursor and Cline. [1] The proposed evaluation configuration is npx -y @mozilla/firefox-devtools-mcp@0.10.6 --tool-preset developer --viewport 1280x720 --start-url http://localhost:3000. [1] Mozilla announced 0.10.6 on October 16, 2026, documenting PDF output through print_page and profile reuse changes. [2] According to Mozilla, select_page and close_page now target the tab identified in the last tab listing, even if tabs have since opened or closed. [2]
Browser debugging tool
Firefox DevTools MCP
VerdictWait and see
Preliminary assessment based on documentation: Firefox DevTools MCP 0.10.6 merits evaluation before developers rely on it to verify fixes.
- Best for
- Developers investigating Firefox-specific bugs who can evaluate agent workflows against controlled fixtures
- Pricing
- Open-source software under MIT or Apache 2.0 licensing; client and model costs are unspecified [1]
Pros
- Mozilla-documented developer preset with debugging, network, console and profiler tools [1]
- According to Mozilla, select_page and close_page now target the tab identified in the last tab listing, even if tabs have since opened or closed. [2]
- Mozilla-documented PDF output using print CSS [2]
- Mozilla-documented reuse of server-created profiles through --profile-path [2]
- Local deployment with MIT or Apache 2.0 licensing [1]
Cons
- Mozilla warning that agents can access browser cookies and sessions [1]
- Script evaluation included in the default basic preset, according to Mozilla [1]
- Unloaded restored tabs omitted from listings, according to Mozilla [2]
- Profile reuse subject to Mozilla’s marker-file and subfolder rules [2]
Why it matters
For agent debugging and regression testing, verifying a fix should require network evidence, correct state and successful UI behavior; console silence alone is insufficient. Chrome DevTools MCP documents comparable inspection and performance tracing, while Playwright MCP offers isolated sessions and storage-state loading for repeatable fixtures. [3][4] Browser permissions matter: Mozilla warns that agents can access cookies and sessions, and says basic includes evaluate_script while slim removes it. [1] An overall assessment remains pending controlled tests. These would cover error reproduction, patch verification, setup friction, approvals, tab targeting, persistence, attachment and PDF correctness. Tests would use the same fixtures, prompts and model across Firefox and Chrome.
Attribution
Sources
- 1MozillaFirefox DevTools MCP repository
- 2Mozilla DiscourseFirefox DevTools MCP 0.10.6 released
- 3ChromeDevToolsChrome DevTools MCP repository
- 4MicrosoftPlaywright MCP repository
Read the original source for full details and context.
AI
Mozilla says Firefox DevTools MCP 0.10.6 adds PDF export and revises tab targeting
Mozilla announced Firefox DevTools MCP 0.10.6 on October 16, 2026. The update adds PDF export, fixes reuse of MCP-created profiles and revises tab selection and closure.
Article · AI
Evaluate AI code reviewers with ReviewBench and private pull requests
GitHub’s ReviewBench provides a public starting point for comparing AI code reviewers. This guide explains its scoring and outlines a private evaluation that measures missed bugs, false alarms, and investigation effort.
Article · AI
Beam deployment costs depend on precision, context and accepted fixes
Hugging Face advertises four-A100 and four-H100 Beam configurations at $10 and $40 per hour. This analysis separates those rates from nominal checkpoint and cache calculations, then sets out how to compare hosted APIs, managed endpoints and rented hardware by cost per accepted fix.