What problem does it solve? Deploying the PingOne Privilege AI Gateway (agentless MCP gateway) on a Kubernetes cluster involves non-obvious failure modes — SSE vs /mcp transport mismatches, stale packaged Helm charts silently dropping sidecars, in-memory DCR client loss on restart, and misleading policy-denial errors — that this Skill diagnoses and resolves with observed, verified commands. ## Core Features & Use Cases - Gateway Deployment: Install and upgrade the agentless-mcpgw Helm release with OIDC secrets, enrollment tokens, and ingress configuration on the SE DevOps cluster. - Agentic App Registration: Register MCP servers in the Privilege console using the correct /sse backend URL, mesh cluster ID, and sidecar pattern via extraContainers. - Symptom Diagnosis: Map errors like "Unknown client", "Gateway Unreachable — initialize: Unauthorized", and "Access Denied for" to their real root causes using gateway logs. - Use Case: A client hangs forever connecting to the gateway — the Skill identifies that svc.cluster.local only resolves inside the cluster and provides the correct external client URL and port-forward workaround. ## Quick Start Diagnose why my MCP client gets "Gateway Unreachable — Error discovering MCP server: calling initialize: Unauthorized" when registering my server with the Privilege gateway.