Radar MCP server
Commit Nov 15, 2026Lets an AI client inspect Kubernetes clusters for issues, topology, events, changes, logs, Helm, and audits.
Also known as skyhook-io/radar, radar
- Stars
- 4,126
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.20.3
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is Radar MCP?
Radar lets an AI client inspect Kubernetes clusters for issues, topology, events, changes, logs, Helm, and audits.
Summary generated from the project's README
About Radar MCP server
Observing Kubernetes cluster health and troubleshooting resource relationships is what Radar enables for DevOps engineers and platform teams. By providing an MCP server, it allows AI agents to access high-level cluster intelligence rather than just raw YAML. This helps agents understand topology, recent resource changes, and deduplicated events to reach diagnoses much faster than using standard command line tools.
Users can run Radar as a single binary on a laptop, a kubectl plugin, or via Helm for in-cluster deployment. It connects to your existing Kubernetes API using your local kubeconfig and requires no external accounts or cloud sync. For security, you can choose between a read-only endpoint to prevent accidental changes or a full endpoint that includes tools for scaling, restarting, or rolling back resources. The server works with various clients including Claude Code, Cursor, and GitHub Copilot.
What you can do with it
- 1Diagnose failed deploymentsAsk an AI agent to explain why a specific rollout or deployment is failing by analyzing logs and recent changes.
- 2Analyze cluster topologyHave an AI client map out how services, pods, and owners connect to understand the impact of a failure.
- 3Automate cluster investigationsTrigger an automated investigation through the CLI to generate a findings report with evidence.
Written from the project's README. Every use case is checked against a quote from it.
How to install Radar MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Radar MCP in Claude Code
$ claude mcp add radar -- docker run -i --rm ghcr.io/skyhook-io/radar:1.20.3Install Radar MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"radar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/skyhook-io/radar:1.20.3"
]
}
}
}Install Radar MCP in VS Code
.vscode/mcp.json
{
"servers": {
"radar": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/skyhook-io/radar:1.20.3"
]
}
}
}Install Radar MCP in VS Code CLI
$ code --add-mcp '{"name":"radar","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/skyhook-io/radar:1.20.3"]}'Install Radar MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"radar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/skyhook-io/radar:1.20.3"
]
}
}
}Install Radar MCP in Codex
$ codex mcp add radar -- docker run -i --rm ghcr.io/skyhook-io/radar:1.20.3Install Radar MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.radar] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/skyhook-io/radar:1.20.3"]
Install Radar MCP in Gemini CLI
$ gemini mcp add -s user radar docker -- run -i --rm ghcr.io/skyhook-io/radar:1.20.3Install Radar MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"radar": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/skyhook-io/radar:1.20.3"
]
}
}
}Automated checks
Ran Nov 12, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHubRadar
The missing open-source Kubernetes UI, with a built-in MCP server for your AI agent. Single binary. No account required. Free forever.
🌐 radarhq.io · Docs · Benchmarks · Releases
Radar shows you what's broken in a Kubernetes cluster, why, and what changed: issues, topology, a timeline of events and resource changes, Helm, GitOps, traffic, audit, and upgrade impact. Your AI agent reads the same cluster data and relationships through Radar's MCP server, and Radar can run an AI investigation for you with the agent CLI you already use. It runs on your laptop as a kubectl plugin or desktop app, or in-cluster with Helm.
- Why Radar? · Debugging in the UI
- AI agents: MCP server and AI investigations — Connect your agent · AI investigations · Benchmarks
- Installation
- Usage
- Views — Issues · Topology · Resources · Image Filesystem · Timeline · Helm · Compare · TLS · GitOps · Traffic · Metrics · Capacity · Cost · Audit · Network path · Upgrade impact · RBAC · Auth
- Supported Resources & Integrations
- Keyboard Shortcuts
- Security
- Development · Contributing
Install and run in 30 seconds:
curl -fsSL https://get.radarhq.io | sh && kubectl radar
Or brew install kubectl-radar. Windows, Krew, desktop app and Helm ↓
Then, with Radar running, connect your AI agent (read-only):
claude mcp add --transport http radar http://localhost:9280/mcp-readonly
Codex, Cursor, GitHub Copilot, other clients, and the desktop app ↓
Why Radar?
- Nothing to install in your cluster — a single binary on your laptop that talks to the Kubernetes API with your kubeconfig. No agents, no CRDs, no dependencies
- Fast on big clusters — tested on tens of thousands of pods; watches the cluster through informers and pushes live updates to the browser over SSE
- Private by design — your cluster data stays on your machine. No account, no agents, no cloud sync. Usage reporting is off unless you opt in, and then sends only anonymous usage counts and coarse cluster facts: Kubernetes version, platform, node-count range, known integrations (what Radar sends). An AI agent you connect sends what it reads to its own model provider
- Airgapped-friendly — runs as a single binary against the Kubernetes API and works in locked-down environments with outbound egress blocked
- Works everywhere — GKE, EKS, AKS, minikube, kind, k3s, or any conformant cluster
- One model of the cluster, for you and your agent — the UI, the MCP server, and AI investigations read the same live data: relationships, health, events, and changes
- Ready for teams — deploy in-cluster with Helm for shared access, with SSO (OIDC or an auth proxy) and per-user Kubernetes RBAC in the open-source build
"Have Radar deployed at work. As far as Kubernetes dashboards go, this is one of the best." — u/TheRealNetroxen
Debugging in the UI
Start from Issues, a ranked queue of what's broken right now. Open a failing resource to see it in context: its owners, Pods, Services, and config on the Topology, what changed and when on the Timeline (with diffs), and its events, logs, and YAML in the detail drawer. Helm, GitOps, and Traffic cover how it got deployed and who talks to it. When you want help, Investigate hands the same evidence to your agent (AI investigations). Radar records resource changes while it watches the cluster; history is in memory by default, and --timeline-storage=sqlite or postgres keeps it across restarts.
AI agents: MCP server and AI investigations
Pointed at raw kubectl, an agent spends its context window on YAML and its time on round trips. Radar's built-in Model Context Protocol (MCP) server gives it what Radar already knows instead: how resources connect, what is unhealthy, deduplicated events, recent changes with diffs, and filtered logs. In our benchmarks, the same agent and model reached a diagnosis about 3× faster through Radar than through kubectl (details).
Connect your agent
MCP is on by default and served on the same port as the UI: 9280 unless you set --port. The desktop app picks its own port: copy the URL from Radar's MCP dialog and change the final /mcp to /mcp-readonly. Start with the read-only endpoint:
# Claude Code
claude mcp add --transport http radar http://localhost:9280/mcp-readonly
# Codex
codex mcp add radar --url http://localhost:9280/mcp-readonly
Setup for Cursor, VS Code (GitHub Copilot), Copilot CLI, OpenCode, Google Antigravity, Kiro, JetBrains, Cline, Devin, Claude Desktop, Zed, Gemini CLI, and any other MCP client is in the MCP guide. Its examples use /mcp; use /mcp-readonly instead to keep Radar's tools read-only. Your agent's other tools follow its own configuration.
- Context, not raw YAML — topology, health assessments, events, changes, and logs, minified so they don't burn the context window. The tools cover resources and topology, issues, events and changes, logs, Helm, audit, upgrade readiness, RBAC, cost, and Prometheus
- You pick the endpoint —
/mcp-readonlyhas no write tools. The full/mcpendpoint, also on by default, adds write tools (restart, scale, apply, rollback, GitOps sync, node drain) marked destructive so clients can ask before running them. On/mcp,diagnosecan also run an in-cluster reachability probe that creates short-lived pods. Calls use Radar's Kubernetes access: your kubeconfig locally, or each user's own RBAC when authentication is on.--mcp-read-onlyturns/mcpoff (and with it, applying a fix from an AI investigation);--no-mcpturns MCP and AI investigations off. Neither blocks ordinary UI writes - Secret values are withheld — Secret reads never include
.dataor.stringData. Environment variables, Helm values, and logs are scrubbed for known secret patterns, which can't catch everything, and the opt-inexec_podtool returns raw command output. See MCP security
AI investigations
Radar can also run the investigation for you, with the agent CLI you already have — Claude Code, Codex, Cursor, or OpenCode — on your machine and signed in with your own account. Radar needs no API key of its own. Start one from a resource's Investigate action, from an issue, by describing what you're seeing on the AI investigations page (where to start, since when, and optionally the resource it's about), or from a terminal against a running Radar:
radar diagnose deploy/checkout -n shop
radar diagnose deploy/checkout -n shop --json > conclusion.json
Every investigation ends on the same Findings page, with the evidence behind each claim. Radar's investigation tools can only read the cluster, and Radar applies a fix only when you approve it, from an investigation of the resource it changes. What else the agent can do depends on how Radar runs it. Radar safeguards (Claude Code and Codex) shuts off the agent's other MCP servers and its ability to write. Your agent setup (the only option for Cursor and OpenCode) runs the agent with its normal configuration, tools, and MCP servers, which Radar cannot constrain and which may be able to change your cluster. Cursor and OpenCode approve tool requests automatically in these runs, without asking you. See agents and isolation.
Investigations need a supported agent CLI on the machine running Radar, MCP on, and authentication off. In-cluster installs don't run them. See the AI investigations guide and agent CLI setup.
Benchmarks
Three studies of an AI agent diagnosing live faults from SREGym (Microsoft and UIUC) on a 3-node EKS cluster, with the same judge scoring every tool. Times are averages to a submitted answer, right or wrong. These are our own benchmarks; compare numbers within a study, not across studies.
| Study | Faults | Result |
|---|---|---|
| Radar MCP vs raw kubectl — same agent and model | 50 | 64s vs 191s to a diagnosis (about 3× faster); 86% vs 60% diagnosed correctly within two minutes |
| Kubernetes MCP servers — Radar, containers/kubernetes-mcp-server, Flux159/mcp-server-kubernetes, Amazon EKS MCP Server, k8sgpt, raw kubectl | 25 | Radar took 57s, 2.3× faster than the next-fastest MCP server; on the 14 faults every tool got right, 33s vs 58s for the next-fastest |
| AI SRE tools — Claude Code + Radar MCP vs kubectl-ai, HolmesGPT, OpenSRE, kagent, AWS DevOps Agent | 50 | Claude Code + Radar MCP was the most accurate (44/50 correct), fastest (79s), and cheapest ($0.27 a fault) |
Per-scenario scores and timings are downloadable from the benchmark pages; the AI SRE study also includes costs.
Installation
Quick Install:
curl -fsSL https://get.radarhq.io | sh
Homebrew:
brew install kubectl-radar
Also available from our tap: brew install skyhook-io/tap/radar.
Then run: kubectl radar. Quick install, PowerShell, Homebrew, and Scoop also set up the radar shorthand. Krew and direct downloads use kubectl radar unless you add your own radar symlink.
CLI
Krew (kubectl plugin manager):
kubectl krew install radar
Scoop (Windows):
scoop bucket add skyhook https://github.com/skyhook-io/scoop-bucket
scoop install radar
PowerShell (Windows):
irm https://get.radarhq.io/install.ps1 | iex
Custom install location (macOS/Linux):
curl -fsSL https://get.radarhq.io | INSTALL_DIR="$HOME/.local/bin" sh
Quick install writes to /usr/local/bin unless INSTALL_DIR says otherwise. The directory is created if missing, and needs to be on your PATH for radar and kubectl radar to resolve.
Direct download — GitHub Releases for macOS, Linux, or Windows.
Desktop App
Native desktop app — no terminal needed.
Homebrew (macOS):
brew install --cask skyhook-io/tap/radar-desktop
Debian/Ubuntu — download the .deb from GitHub Releases, then:
sudo apt install ./radar-desktop_*.deb
Fedora/RHEL — download the .rpm from GitHub Releases, then:
sudo dnf install ./radar-desktop_*.rpm
Linux (AppImage, any distro) — download the .AppImage from GitHub Releases, then:
chmod +x radar-desktop_*_linux_amd64.AppImage
./radar-desktop_*_linux_amd64.AppImage
The AppImage doesn't update itself. When a new version is out, Radar links to the download.
Kubeconfig login plugins (exec) run from inside the AppImage, not from the folder you started it in. If a plugin's args name a file by a relative path, such as --token-file token.json, the plugin can't find it and Radar shows "Authentication Failed". Give the full path instead, such as --token-file /home/you/.kube/token.json. A relative command, such as ./token.sh, works: it's looked up next to the kubeconfig file.
Scoop (Windows):
scoop bucket add skyhook https://github.com/skyhook-io/scoop-bucket
scoop install radar-desktop
Windows (direct download) — GitHub Releases.
In-Cluster Deployment
Deploy to your cluster for shared team access:
helm repo add skyhook https://skyhook-io.github.io/helm-charts
helm install radar skyhook/radar -n radar --create-namespace
See the In-Cluster Deployment Guide for Gateway API and ingress exposure, authentication, and RBAC configuration.
Usage
# Opens browser automatically
kubectl radar
# Quick install, PowerShell, Homebrew, and Scoop also set up the bare command
radar
Common flags
| Flag | Default | Description |
|---|---|---|
--kubeconfig |
~/.kube/config |
Path to primary kubeconfig file |
--namespace |
(context namespace) | Initial namespace filter (supports multi-select in the UI; also used as RBAC fallback for namespace-scoped users). Unset, Radar uses your saved pick, then the kubeconfig context's namespace, then all namespaces |
--port |
9280 |
Server port |
--listen-address |
127.0.0.1 |
HTTP listen IP address (IPv4 or IPv6), or localhost. Bind a specific local IP or use 0.0.0.0 for all interfaces. Non-loopback access needs authentication and network controls. |
--no-browser |
false |
Don't auto-open browser |
--timeline-storage |
memory |
Timeline storage backend: memory, sqlite, or postgres |
--disable-exec |
false |
Disable pod terminal, debug shells, pod file browsing, CloudNativePG sessions and MCP exec_pod |
--auth-mode |
none |
Authentication mode: none, proxy, or oidc (details) |
--no-mcp |
false |
Disable all MCP endpoints |
--mcp-read-only |
false |
Expose only read-only MCP tools; disable /mcp (env: RADAR_MCP_READ_ONLY) |
The Configuration Guide describes every startup flag in the table above and 27 more, plus tuning for slow or high-latency clusters, kubeconfig precedence, and context switching.
--kubeconfig-dir, --namespaces, --namespace-scope, --base-path, --allowed-hosts, --trusted-origins, --browser, --timeline-db, --timeline-max-size, --history-limit, --disable-helm-write, --disable-local-terminal, --debug-image, --list-page-size, --context-switch-timeout, --first-paint-backstop, --namespace-list-timeout, --max-scope-candidates, --prometheus-url, --prometheus-single-cluster, --prometheus-cluster-label, --prometheus-header, --prometheus-header-from-env, --beyla-job-selector, --opencost-currency, --mcp-catalog-stdio, --version
radar --help is authoritative for the installed version. radar cloud status inspects an in-cluster Radar Cloud installation without changing it (details).
Views
Issues
One ranked queue of what's broken right now — crash loops, image pull failures, stuck rollouts, pods that can't be scheduled, dangling references, and failing Argo CD / Flux conditions — each with an Investigate action. See Issues.
Topology
Interactive graph showing how your Kubernetes resources are connected in real-time.
- Two modes: Resources (full hierarchy) and Traffic (network flow path)
- Group by namespace, app label, or view ungrouped
- Filter by resource kind — click any node for full details
- Auto-layout powered by ELK.js, live updates via SSE
Resources
Table-based resource browser with smart columns per resource kind.
- Browse all resource types including CRDs
- Inspect CRD definitions, versions, instances, and searchable schemas
- Search by name, filter by status or problems (CrashLoopBackOff, ImagePullBackOff, etc.)
- Add custom columns from any label or annotation — sortable, filterable, and resizable
- Click any resource for YAML manifest, related resources, logs, and events
- Set regular or init-container images on Deployments, StatefulSets, DaemonSets, and Argo Rollouts, with live rollout progress in tables, drawers, workload views, and Applications
Image Filesystem Viewer
Inspect container image filesystems directly from the Pod view — no need to pull images locally or exec into containers.
- Browse, search, and download files from any container image in a Pod
- Works with public images (Docker Hub, Quay, GHCR) and private registries (GCR, ECR, ACR) using your cluster's ImagePullSecrets
See Image filesystem.
Timeline
Unified timeline of Kubernetes events and resource changes.
- Filter by event type (all or warnings only)
- Resource change diffs showing what changed (replicas, images, etc.)
- Real-time updates as new events occur
Helm
Manage Helm releases deployed in your cluster — inspect values and rendered manifests, diff revisions, see why an upgrade or hook failed, then upgrade, roll back, or uninstall. Radar tracks available chart upgrades from your configured repos or your own OCI registries. See Helm Support for the detailed behavior and limits.
Compare Resources
Diff any two Kubernetes resources of the same kind side-by-side — like comparing a staging Deployment to its production sibling, or two pods that should be identical but aren't. Server-assigned noise (managedFields, resourceVersion, last-applied) is stripped, and diff-only and spec-only modes cut the rest. See Compare.
TLS Certificate Management
View TLS certificate details and expiry dates across all namespaces — catch expiring certificates before they cause outages.
- Parses TLS secrets to show certificate subject, issuer, and validity period
- Dashboard-level certificate expiry overview
- Available from the resource detail view for any TLS-type Secret
GitOps
Monitor, diagnose, and manage FluxCD and ArgoCD resources in one place.
- Fleet view + per-app detail page for ArgoCD (
Application,ApplicationSet,AppProject) and FluxCD (GitRepository,OCIRepository,HelmRepository,Bucket,Kustomization,HelmRelease,Alert) - Diagnosis — field-level drift, recent events per resource, stuck-drift-loop detection, parsed operation failures, one-click remediation
- Sync, suspend, resume, reconcile, and rollback from the UI or through MCP
See the GitOps guide for the full feature matrix, RBAC requirements, demo cluster, and single-cluster scope notes.
Radar MCP questions
How do I add Radar MCP to Claude Code?
Run claude mcp add radar -- docker run -i --rm ghcr.io/skyhook-io/radar:1.20.3 in your terminal. Add --scope user to make it available in every project.
How do I add Radar MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I connect Claude Code to Radar's MCP server?
Run the claude mcp add command against Radar's read-only endpoint on port 9280, or use the full /mcp endpoint if you need write tools.
What is the difference between the /mcp and /mcp-readonly endpoints?
The read-only endpoint has no write tools; the full endpoint adds destructive write tools like restart, scale, apply, and rollback.
Does Radar's MCP server expose Kubernetes Secret values?
No, Secret reads never include .data or .stringData, and other outputs are scrubbed for known secret patterns.
Does Radar require an account or API key for AI investigations?
No, investigations use the agent CLI you already have, signed in with your own account.
On what port does Radar serve MCP?
MCP is on by default on port 9280 unless you change it with --port.