K8scortex 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.

  const tokenEndpoint = process.env.IDENTITY_ENDPOINT || "http://169.254.169.254/metadata/identity/oauth2/token";

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 k8scortex-mcp -- npx -y k8scortex-mcp

{
  "mcpServers": {
    "k8scortex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "k8scortex-mcp"
      ]
    }
  }
}

[mcp_servers.k8scortex-mcp]
command = "npx"
args = ["-y", "k8scortex-mcp"]

{
  "mcpServers": {
    "k8scortex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "k8scortex-mcp"
      ]
    }
  }
}

{
  "servers": {
    "k8scortex-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "k8scortex-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: KUBECONFIG (Path to your kubeconfig file. Each context becomes a cluster. Defaults to ~/.kube/config), CLUSTERS_CONFIG (Optional path to a cluster registry JSON file mixing kubeconfig, EKS, GKE and Key Vault clusters), K8SCORTEX_STDIO_ROLES (Roles for the local session, e.g. 'developer' for read-only tools. Defaults to platform-engineer).