CoS Codex Bridge MCP Server

What the code does

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

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(process.execPath,[fileURLToPath(new URL(worker,import.meta.url)),this.config.configPath,id],{detached:true,stdio:'ignore',env:process.env});

  const parent=await project(this.config,args.parent);const dest=path.join(parent,args.name);

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 cos-codex-bridge -- npx -y cos-codex-bridge

{
  "mcpServers": {
    "cos-codex-bridge": {
      "args": [
        "-y",
        "cos-codex-bridge"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.cos-codex-bridge]
command = "npx"
args = ["-y", "cos-codex-bridge"]

{
  "mcpServers": {
    "cos-codex-bridge": {
      "args": [
        "-y",
        "cos-codex-bridge"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "cos-codex-bridge": {
      "args": [
        "-y",
        "cos-codex-bridge"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: COS_BRIDGE_CONFIG (Absolute path to the private config.json created by the CoS Codex Bridge installer.). The author declared them in the registry entry; get the values from the project itself.