Radar MCP
An open-source Kubernetes UI with a built-in MCP server: the agent inspects the cluster, diagnoses breakages and operates it with RBAC in mind
- 4,118 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Gives the agent access to the Kubernetes cluster
- Write operations affect the real cluster
- Optional route probing creates temporary pods
Install
- Works in
Manual install
curl -fsSL https://get.radarhq.io | sh && kubectl radarInstalls a single binary and starts Radar. The MCP server is enabled by default at http://localhost:9280/mcp.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Gives the agent access to the Kubernetes cluster
- Write operations affect the real cluster
- Optional route probing creates temporary pods
This is third-party code. Review the repository files before installing.
What it does
Radar is an open-source Kubernetes UI in a single Go binary: topology, resources, event timeline, Helm, GitOps, live service traffic, cost and cluster audits. Its built-in MCP server lets the agent work with the cluster not through raw kubectl but through token-optimized tools: resources are stripped of noise, data is enriched with a topology graph, health assessment and filtered logs. Diagnosis is read-only by default, while write tools such as restart, scale, apply and rollback are flagged for confirmation and enforced through the cluster's RBAC. Secrets are not exposed, and environment values and logs are scrubbed of keys. It runs from a laptop or in-cluster via Helm.
Who it is for. For DevOps and SRE engineers and developers who want Kubernetes inspection and troubleshooting through an agent.
Good fit when
- You want the agent to inspect the cluster and explain what broke and why
- You want cluster operations over MCP with confirmation and RBAC
- You want the agent to reach topology, events, Helm and GitOps without raw kubectl
Not a fit when
- You cannot give the agent cluster access even with RBAC
- You only need the visual UI without an agent connection
Example request
Inspect the cluster, find pods in crashloop and explain what changed before the failureMCP
- Transport
- http
- Authentication
- not required
Limitations
The MCP server works with your kubeconfig permissions and is bounded by the cluster's RBAC. Write operations affect the real cluster; they are flagged for confirmation, but the confirmation is your responsibility. Optional in-cluster route probing spins up short-lived, self-deleting pods. The MCP server is enabled by default and turned off with a flag.
How to disable. Run Radar with the --no-mcp flag to disable the MCP server and remove its address from the agent config.
FAQ
Why MCP over raw kubectl?
Responses are stripped of noise and enriched with topology, health and filtered logs; diagnosis is read-only by default, and changes go through confirmation and RBAC.
Are secrets exposed?
No. Secret data is not returned, and environment values and logs are scrubbed of keys and tokens.
Discussion
No questions or reviews yet.
Related
MCP serversKubernetes MCP
MCP Server Kubernetes
MCP server for managing a Kubernetes cluster through kubectl and Helm, with a non-destructive mode
A Go MCP server for Kubernetes and OpenShift: resources, pods, logs, Helm and Tekton straight through the cluster API
An MCP server and skills on top of Kubernetes network observability: an agent investigates incidents and queries cluster traffic through an eBPF-built index
A Go MCP server for Kubernetes: read any cluster resource and pod logs, with apply and exec in write mode
MCP server for Kubernetes: the agent reads cluster state, diagnoses pod failures and runs operations through kubectl
K8M MCP gives an agent conversational access to Kubernetes resources, pod logs and operations across multiple connected clusters.
README in short
The README describes Radar as an open-source Kubernetes UI in a single Go binary that runs from a laptop or in-cluster with no agents or CRDs. Views: topology, resources, timeline, Helm, compare, TLS, GitOps, traffic, cost, audit, upgrade impact, RBAC and MCP. The built-in MCP server gives agents token-optimized, safe tools with enriched data and RBAC awareness, served over HTTP on the port from the --port flag. Cluster data stays on the machine, with no account or cloud sync. Apache-2.0 licensed.