EZO Watcher MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  if (exists('/.dockerenv')) return 'docker'

  const child = spawn(bin, ['tunnel', '--url', local], { stdio: ['ignore', 'pipe', 'pipe'] })

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ezo-watcher -- npx -y ezo-watcher

{
  "mcpServers": {
    "ezo-watcher": {
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ]
    }
  }
}

[mcp_servers.ezo-watcher]
command = "npx"
args = ["-y", "ezo-watcher"]

{
  "mcpServers": {
    "ezo-watcher": {
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ]
    }
  }
}

{
  "servers": {
    "ezo-watcher": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ezo-watcher"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: WATCHER_MCP_TOKEN (Token for the running Watcher's /mcp endpoint. When unset it is read from the project's .watcher/.env).