Chromecast / DLNA casting (catt) MCP Server

What the code does

We read the source, 19 h ago · rules ccca72095570

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.

            result = 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.

            result = subprocess.run(

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 catt-mcp -- uvx catt-mcp

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

[mcp_servers.catt-mcp]
command = "uvx"
args = ["catt-mcp"]

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

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

This one needs environment variables set before it will start: CATT_DEVICE (Name or IP of the default Chromecast / DLNA device), TV_HOST (Optional Android TV IP, used to wake the screen over ADB before casting), ADB_PATH (Path to the adb binary if not on PATH). The author declared them in the registry entry; get the values from the project itself.