🐋 Can this dev-tools MCP work via Docker instead of locally installed node?

[PureKrome]

👋🏻 G'Day CDT!

Thank you kindly for providing this tool.

In the Requirements and Getting Started documentation it suggests that node needs to be installed locally. Putting aside language wars, etc .. is it possible that this MCP tool can be provided as a Docker image? I'm really really new to MCP's so I apologize if this cannot be technically possible.

Keep up the awesome work! 🎉

EDIT: I'm guessing that the complexity here could be because

• dev-tools actually runs a chrome instance / connects to an existing instance
• really hard for docker to 'punch out' of it's instance and then connect to the local machine + start a chrome instance, etc

I hoping hard doesn't mean impossible

[OrKoN]

We currently do not plan to provide a docker image but it is definitely possible to run the MCP server in a Docker container with Chrome. See Puppeteer Dockerfile as an example https://github.com/puppeteer/puppeteer/tree/main/docker Although we only support the stdio transport so you would need a proxy to expose the MCP to the network.

[kth8]

Installing chrome-devtools-mcp via npx during runtime inside a container works fine, e.g.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chrome-devtools": {
      "type": "local",
      "command": [
        "podman",
        "run",
        "--rm",
        "-i",
        "--init",
        "docker.io/library/node:lts-alpine",
        "npx",
        "-y",
        "chrome-devtools-mcp@latest",
        "--browser-url=http://192.168.0.3:50001"
      ],
      }
    }
  }
}