SSyncDev

Zen DevTools MCP Server

Attach Firefox DevTools automation to the Zen or Firefox window you already have open, tabs and all.

Local server

What is the Zen DevTools MCP Server?

Most browser automation starts a fresh, empty profile. That is fine for tests and frustrating for debugging, because the bug you care about usually lives in the tab you already have open, signed in, with your extensions loaded. The Zen DevTools MCP server exists to close that gap for people on Firefox-family browsers.

It is a thin wrapper around Mozilla's Firefox DevTools MCP. Rather than launching a throwaway instance, it connects that server to the Zen Browser, Firefox or fork you are already using.

The Marionette problem it solves

Attaching to a live Firefox needs Marionette, the browser's remote-control protocol, and Marionette can only be switched on at launch. Opening Zen from the Dock does not do that. So the wrapper checks the port first. If nothing is listening, it quits the browser gracefully, relaunches it with --marionette, waits for the port to come up, and only then hands over to the underlying server with --connectExisting --enableScript.

Session restore brings your tabs back. The restart happens once; after that, the port is already open and the wrapper simply attaches.

Configuration flags

Flag Default Purpose
--app Zen macOS app name used to quit and reopen the browser
--process zen process name checked with pgrep -x
--port 2828 Marionette port to probe and listen on

To point it at regular Firefox, pass --app Firefox --process firefox. Running Zen and Firefox side by side means giving one of them a different port, such as 2829, and registering two entries in your client.

Running it

There is no package to install. The server runs straight from its Git source through npx github:sushruth/zen-devtools-mcp or the bunx equivalent, so Node.js or Bun must be present. Claude Code accepts the JSON entry through claude mcp add-json or a project .mcp.json file.

The browser tools themselves come from the wrapped Firefox DevTools server. This project adds no tools of its own; its job is getting the connection to succeed against a browser you did not start from the terminal.

Limits worth knowing

  • macOS only. It relies on open, osascript and pgrep.
  • The first attach restarts your browser. Save anything unsaved in open forms before you let an agent connect.
  • Script execution is enabled when it starts the underlying server, so an assistant can run JavaScript in your real, logged-in session. Treat that with the same care as handing someone your unlocked laptop.

If you use Chrome instead, the Chrome DevTools server covers similar ground, and Playwright suits scripted, clean-profile runs. More options sit in our developer tools category.

How to install the Zen DevTools MCP Server

{
  "mcpServers": {
    "zen-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "github:sushruth/zen-devtools-mcp"
      ]
    }
  }
}

Requires Node.js for npx. Add "--app", "Firefox", "--process", "firefox" to args to target Firefox instead of Zen. macOS only.

Frequently asked questions

Marionette, the remote-control protocol it needs, can only be enabled when the browser launches. If the port is not open, the wrapper quits the browser, relaunches it with --marionette and waits for the port. Session restore brings your tabs back.