Rancher MCP Server

What the code does

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

    return subprocess.run(  # noqa: S603

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

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

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

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

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

This one needs environment variables set before it will start: RANCHER_URL (Rancher server URL (single-instance mode)), RANCHER_TOKEN (Rancher API token (token-xxxxx:yyyyyyyyy)), RANCHER_VERIFY_SSL (Verify TLS certificates (default true)), RANCHER_INSTANCES_JSON (Multi-instance config JSON (overrides single-instance mode; supports per-instance read_only)). The author declared them in the registry entry; get the values from the project itself.