Physical Capability Cloud MCP Server

What the code does

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

        return reply.type("text/html").send(readFileSync(indexPath, "utf-8"));

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 proc = spawn(this.config.pythonPath, ["-m", "pcc_plr_sidecar"], {

            r = subprocess.run(

                cmd, shell=True, capture_output=True, text=True, timeout=timeout,

  q.innerHTML=active.map(j=>{

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

claude mcp add physical-capability-cloud --transport http https://capability.network/mcp

{
  "mcpServers": {
    "physical-capability-cloud": {
      "url": "https://capability.network/mcp"
    }
  }
}

[mcp_servers.physical-capability-cloud]
url = "https://capability.network/mcp"

{
  "mcpServers": {
    "physical-capability-cloud": {
      "url": "https://capability.network/mcp"
    }
  }
}

{
  "mcpServers": {
    "physical-capability-cloud": {
      "url": "https://capability.network/mcp"
    }
  }
}

Endpoints