Verdi Bridge MCP Server

What the code does

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

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.

                proc = subprocess.run(self._command(), input=self._preamble() + payload, text=True,

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.

                    self._process = subprocess.Popen(

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 verdi-bridge -- uvx verdi-bridge

{
  "mcpServers": {
    "verdi-bridge": {
      "command": "uvx",
      "args": [
        "verdi-bridge"
      ]
    }
  }
}

[mcp_servers.verdi-bridge]
command = "uvx"
args = ["verdi-bridge"]

{
  "mcpServers": {
    "verdi-bridge": {
      "command": "uvx",
      "args": [
        "verdi-bridge"
      ]
    }
  }
}

{
  "servers": {
    "verdi-bridge": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "verdi-bridge"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: VERDI_BRIDGE_DIR (Private bridge directory on the Verdi host; omit to use the default ~/.verdi-bridge/session), VERDI_BRIDGE_HOST (SSH user@host; omit for a local Verdi GUI), VERDI_BRIDGE_CONTROL_PATH (Optional existing SSH ControlMaster socket path).