mcp-firefox
Allows interaction with Firefox via its Remote Debugging Protocol, providing tools to evaluate JavaScript, navigate tabs, capture network traffic, take screenshots, and extract page content.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-firefoxtake a full page screenshot of the current tab"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-firefox
An MCP (Model Context Protocol) server that connects to Firefox's Remote Debugging Protocol (RDP) over TCP, exposing browser DevTools capabilities as tools for LLMs.
How It Works
Firefox has a built-in Remote Debugging Protocol that speaks length-prefixed JSON over TCP. This server maintains a persistent connection to that port and translates MCP tool calls into RDP messages, returning the results to the LLM.
LLM ↔ MCP (HTTP :8090) ↔ Firefox RDP (TCP :6000)The RDP client uses a background reader task to handle both request/response pairs and unsolicited events (like network traffic), enabling real-time capture features.
Related MCP server: Firefox DevTools MCP
Tools
Tool | Description |
| Evaluate a JavaScript expression in the current tab's console (supports top-level await) |
| List all open browser tabs with URLs and titles |
| Navigate the current tab to a URL |
| Get the full HTML source of the current page |
| Get cached console messages (errors, logs) |
| Extract readable text content from the page (strips nav, ads, boilerplate) |
| Take a screenshot — viewport, full page, or a specific CSS selector element |
| Start capturing network requests (like opening the Network tab) |
| Read captured network events (URLs, methods, status, timing, optionally bodies) |
| Stop network capture and clean up |
| Send arbitrary RDP JSON for experimentation |
Firefox Setup
1. Enable Remote Debugging
Open about:config in Firefox and set:
Preference | Value | Purpose |
|
| Allow remote debug connections |
|
| Skip the "allow connection?" dialog (optional) |
|
| Enable chrome debugging |
2. Start the Debug Listener
firefox --start-debugger-server 6000This opens a TCP listener on localhost:6000. Your tabs and session restore normally.
3. Verify
ss -tlnp | grep 6000You should see Firefox listening on 127.0.0.1:6000.
Installation
Requires Python 3.11+. Uses uv for dependency management:
uv venv
uv pip install -e .Running
.venv/bin/firefox-mcpThe MCP server starts on http://0.0.0.0:8090/mcp using streamable HTTP transport (stateless mode).
Environment Variables
Variable | Default | Description |
|
| Firefox RDP host |
|
| Firefox RDP port |
MCP Client Configuration
{
"mcpServers": {
"firefox-devtools": {
"url": "http://localhost:8090/mcp"
}
}
}Usage Examples
Page Content & Screenshots
# Read article text from a news site you're logged into
> read_page
# Take a screenshot of a specific element
> screenshot(selector=".article-body")
# Full page screenshot
> screenshot(fullpage=True)Network Capture
Capture API traffic from web apps (streaming services, SPAs, etc.):
# Start recording network traffic
> start_capture
# Navigate to the app or trigger actions
> navigate("https://www.disneyplus.com/home")
# See what API calls were made
> read_capture
# Get response bodies (JSON payloads, manifests, etc.)
> read_capture(include_bodies=True)
# Done
> stop_captureRaw RDP Exploration
> raw_rdp_command({"to": "root", "type": "listTabs"})
> raw_rdp_command({"to": "<consoleActor>", "type": "getCachedMessages", "messageTypes": ["PageError", "ConsoleAPI"]})Use list_tabs first to discover actor IDs, then experiment with raw_rdp_command.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceAn MCP server that exposes Firefox browser automation capabilities through the Model Context Protocol, enabling AI assistants to control web browsers for navigation, interaction, and data collection tasks.Last updated4BSD 3-Clause
- FlicenseBqualityAmaintenanceAutomates Firefox via WebDriver BiDi for browser control, including navigation, screenshot, network capture, and script execution, using natural language through MCP clients.Last updated321,368333
- Alicense-qualityDmaintenanceConnects to a running Chrome instance via CDP to expose browser control as MCP tools, preserving login state, cookies, and extensions for automation.Last updated16MIT
- Alicense-qualityBmaintenanceLets coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.Last updated1,516,580Apache 2.0
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
A paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/murphysean/mcp-firefox'
If you have feedback or need assistance with the MCP directory API, please join our Discord server