← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionFirefox DevTools MCPAutomate Firefox for AI assistants.FSB MCP ServerControl the FSB browser extension from any MCP client for DOM-first AI browser automation.
FMRS58 / 100 · C66 / 100 · C
Reliability10 / 2010 / 20
Security and permissions8 / 2014 / 20
Maintenance13 / 2015 / 20
Documentation14 / 2015 / 20
Setup experience13 / 2012 / 20
Best for
  • Local Firefox automation
  • Web debugging and development workflows
  • Users of Claude Code, Claude Desktop, Cursor, or Cline
  • Developers who want AI clients to directly control the browser
  • Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
  • Multi-client support (Claude Code, Cursor, VS Code, etc.)
  • Internal tools or automation scripts needing browser interaction
Not for
  • Environments without a local Firefox installation
  • Situations where an agent must not access browser-reachable content
  • Cloud-hosted execution environments
  • Direct use with a normal daily-browsing profile
  • Headless browser or server-side monitoring
  • Bypassing website restrictions or unsupervised automation
  • Automation on sensitive pages without human supervision
  • Complex scenarios that require visual understanding (e.g., screenshots)
Required permissions
  • Requires access to a local Firefox browser and sites it can reach.
  • A dedicated Firefox profile is recommended; when connecting to an existing browser, the agent can access cookies, logged-in sessions, and open tabs.
  • The `prefs` and `privileged` modules require `MOZ_REMOTE_ALLOW_SYSTEM_ACCESS=1` and are available only in the Mozilla-internal build.
  • Firefox for Android mode requires adb on PATH and a connected Android device.
  • Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
  • MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
  • Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
  • Uploading files requires providing absolute local paths
Risks and side effects
  • Browser automation servers carry inherent risk and may expose cookies, saved sessions, and browser-reachable content.
  • Web pages may contain prompt injection intended to manipulate the agent; use sites you control or trust.
  • The developer preset enables script and debugging tools, while the mozilla preset additionally expands access to privileged contexts.
  • Connecting to an existing Firefox uses a real browsing session; leaving Marionette enabled during normal browsing can expose navigator.webdriver and trigger bot detection.
  • Browser automation can be unpredictable on complex or sensitive sites; supervision is required
  • Credentials and payment info are stored in a vault but require user unlock flows
  • API keys are encrypted in Chrome storage, but clients may send page context to model providers
  • MCP server is a local process, posing local security risks
  • Capability catalog allows most non-denied origins but is gated by multiple checks
Supported clientsClaude Code, Claude Desktop, Cursor, ClineClaude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex
Tools2830