Metal GPU Trace MCP Server

What the code does

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

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.

         "params": {"name": "compare-layer", "arguments": {"api": "d3d12; rm -rf /"}}},

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.

    proc = subprocess.run(["curl", "-fsSL", "--proto", "=https", "--max-filesize", str(max_bytes), "--max-time", "600",

    env = dict(os.environ, PERF_OUT=str(OUT),

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 metal-gpu-trace -- uvx metal-gpu-trace

{
  "mcpServers": {
    "metal-gpu-trace": {
      "command": "uvx",
      "args": [
        "metal-gpu-trace"
      ]
    }
  }
}

[mcp_servers.metal-gpu-trace]
command = "uvx"
args = ["metal-gpu-trace"]

{
  "mcpServers": {
    "metal-gpu-trace": {
      "command": "uvx",
      "args": [
        "metal-gpu-trace"
      ]
    }
  }
}

{
  "servers": {
    "metal-gpu-trace": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "metal-gpu-trace"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: METAL_TRACE_OUT (Absolute path of the directory where recordings go), METAL_TRACE_WINE (Wine directory holding bin/wine, used when a recording names none).