Skip to main content
Glama
mozilla

firefox-devtools-mcp

by mozilla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to firefox-devtools-mcp

Related Servers

  • marionette-mcp

    bornmw
    A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to drive a user-launched Firefox instance via its native Marionette protocol, providing precise DOM actuation like clicking, typing, uploading files, taking screenshots, and evaluating JavaScript.
    18
    18 npm
    1
    GPL 2.0

  • gecko-mcp

    Frumane
    A
    license
    A
    quality
    C
    maintenance
    Drive Firefox-based browsers (Floorp, LibreWolf, Zen, Waterfox, Mullvad, Firefox) from any MCP client — read pages, screenshot, click, fill forms and manage tabs in your real session, over Marionette/WebDriver. OS input & JS eval locked by default.
    41
    76 npm
    2
    MIT

  • firefox-mcp

    surpasses
    A
    license
    B
    quality
    C
    maintenance
    Lets Claude Code attach to a running, signed-in Firefox over WebDriver BiDi to control tabs, navigate, screenshot, read pages, click, type, fill forms, evaluate JavaScript, and inspect console/network activity.
    22
    MIT

  • LibreWolf Agent Bridge

    Hokondrak
    F
    license
    Not graded
    quality
    B
    maintenance
    Local-first browser automation for LibreWolf, enabling controlled profile browsing with status, navigation, screenshots, console/network inspection, and more through MCP.
    -

  • browser-firefox-mcp

    ironessi
    A
    license
    C
    quality
    B
    maintenance
    Security-focused Firefox browser MCP server for penetration testing, built on Playwright, enabling vulnerability scanning, session manipulation, network inspection, and reconnaissance.
    40
    1
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 34 tools

Disambiguation4/5

Most tools target distinct actions (click, hover, fill, drag, screenshot, dialogs), and descriptions clearly separate page-level vs element-level operations. Minor ambiguity exists between fill_form_by_uid and fill_by_uid, and among get_page_text, take_snapshot, and evaluate_script, but their descriptions provide adequate guidance.

Naming Consistency5/5

Tool names consistently follow a snake_case verb_noun pattern (e.g., list_pages, close_page, install_extension, screencast_start). Even paired and related tools use the same convention, making the naming predictable and scannable.

Tool Count3/5

At 34 tools, the set is large and heavier than ideal for an MCP server, requiring agents to manage a substantial tool list. However, the tools are organized around distinct browser automation concerns and most serve a clear purpose, so the count feels like justified comprehensiveness rather than duplication.

Completeness4/5

The tool surface covers tab lifecycle, navigation, DOM interaction, screenshots, downloads, dialogs, extensions, screencasting, and session management. The main gap is that uninstall_extension references list_extensions, but no list_extensions tool is exposed; network and console inspection tools are also absent, but core browser automation workflows are well covered.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources