Remote Bridge MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        let output = std::process::Command::new("rsync").args(&args).output()?;

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

            "chmod 777", "chmod -r",         // permission changes

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.

postinstall: node scripts/install.js

const child = spawn(binaryPath, process.argv.slice(2), { stdio: 'inherit' });

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 remote-bridge -- npx -y remote-bridge-cli

{
  "mcpServers": {
    "remote-bridge": {
      "args": [
        "-y",
        "remote-bridge-cli"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.remote-bridge]
command = "npx"
args = ["-y", "remote-bridge-cli"]

{
  "mcpServers": {
    "remote-bridge": {
      "args": [
        "-y",
        "remote-bridge-cli"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "remote-bridge": {
      "args": [
        "-y",
        "remote-bridge-cli"
      ],
      "command": "npx"
    }
  }
}