Weboperator MCP Server

What the code does

We read the source, 23 h 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.

    const child = spawn(type === 'clipboard.read' ? '/usr/bin/pbpaste' : '/usr/bin/pbcopy', [], { stdio: ['pipe', 'pipe', 'ignore'] });

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 weboperator -- npx -y weboperator-mcp

{
  "mcpServers": {
    "weboperator": {
      "command": "npx",
      "args": [
        "-y",
        "weboperator-mcp"
      ]
    }
  }
}

[mcp_servers.weboperator]
command = "npx"
args = ["-y", "weboperator-mcp"]

{
  "mcpServers": {
    "weboperator": {
      "command": "npx",
      "args": [
        "-y",
        "weboperator-mcp"
      ]
    }
  }
}

{
  "servers": {
    "weboperator": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "weboperator-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: WEBOPERATOR_BRIDGE_PORT (Port of the local WebOperator bridge HTTP API), WEBOPERATOR_AGENT_SOCKET (Unix socket path the bridge listens on), WEBOPERATOR_API_TOKEN (Shared token required by the bridge when unauthenticated access is disabled).