Firefox DevTools MCP vs Ghostfox
A side-by-side look at the Firefox DevTools MCP and Ghostfox MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Firefox DevTools MCP for browser automation work as a local process; choose Ghostfox for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Firefox DevTools MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
slim, developer, mozilla.
Choose Ghostfox when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 63/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 500 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Firefox DevTools MCP | View Ghostfox |
Tools & capabilities
Firefox DevTools MCP tools 4
slimthe minimum to browse and interact with pagesdeveloperadds tools for web developersmozillaadds tools for Firefox developersallevery module
Ghostfox tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Firefox DevTools MCP
{
"mcpServers": {
"firefox-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"@mozilla/firefox-devtools-mcp@latest"
]
}
}
}
Ghostfox
{
"mcpServers": {
"ghostfox": {
"command": "npx",
"args": [
"-y",
"ghostfox"
]
}
}
}
Frequently asked questions
Firefox DevTools MCP is categorized under Browser Automation and uses a local stdio subprocess. Ghostfox belongs to Browser Automation and uses a local stdio subprocess. Pick Firefox DevTools MCP for browser automation work and Ghostfox for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Firefox DevTools MCP has no declared pricing — check the project's own site. Ghostfox has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add firefox-devtools-mcp and ghostfox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Firefox DevTools MCP has a quality signal of 63/100 (Good) with 0 views, 0 installs and 500 GitHub stars. Ghostfox has 45/100 (Fair) with 0 views, 0 installs and 11 GitHub stars.
