CLI Bridge MCP Server

What the code does

We read the source, 1 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(

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.

        path = os.path.join(config.OVERFLOW_DIR, f"{job_id}.txt")

        proc = subprocess.run(

    base_env = config.strip_nesting(dict(os.environ)) if config.strip_nesting_env() else os.environ

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 cli-bridge-mcp -- uvx cli-bridge-mcp

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

[mcp_servers.cli-bridge-mcp]
command = "uvx"
args = ["cli-bridge-mcp"]

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

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

Optional settings from the registry entry, left out of the block above: CLI_BRIDGE_PROFILE (Cost profile: saver (free-only fan-out, include_paid refused) | balanced (paid only with include_paid) | max (limited/paid join fan-out)), CLI_BRIDGE_TERSE (Response-style preamble level: off | lite (default) | full | ultra), CLI_BRIDGE_CACHE_TTL_S (Response cache TTL in seconds. 0 = off (default)).