running radar locally with mutliple kubeconfigs and mcp

[anishp55]

Describe the bug

not sure if this is a bug or not. but when running radar on you local system with the mcp server enabled, and multiple kubeconfigs set the LLM says it only has access to one cluster, while we can switch between the clusters in the UI, this doesn't update what the MCP has access to

To reproduce

Steps to reproduce the behavior:

1. set the KUBECONFIG to point to multiple clusters.
2. from the same shell start Radar
3. use your tooling of choice to access your llm and access the mcp server
4. ask the llm if it has access to the radar mcp server and list its tools
5. ask it what clusters it has access to, this only returns the first cluster from the KUBECONFIG env var

Expected behavior

when asking using the MCP with multiple KUBECONFIGs i would expect the MCP to return it has access to how ever many clusters were pointed to by the KUEBCONFIG env var.

Screenshots

Diagnostics (optional)

A diagnostics snapshot helps us debug faster — it captures your environment, cluster info, and Radar state automatically. It doesn't include secrets, credentials, or resource contents, but you're welcome to review and redact anything you'd prefer not to share. In Radar, press Ctrl+Shift+D → Copy as Markdown, or click the bug icon (bottom-right corner) → Report Bug.

Diagnostics snapshot

If you'd rather not include diagnostics, these basics help:

• Radar version: 1.8.1
• Kubernetes: 1.35.2
• Codex CLI and Zoo Code - GPT 5.5 and Qwen3.6 for the LLM's

Logs

Paste any relevant logs here

Additional context

Add any other context about the problem here.

[nadaverell]

Thanks for reporting! yeah the MCP is not aware of all the contexts when running locally, I think this is doable but would require switching context to actually access data from another cluster. Radar has a lot of design assumptions and optimizations right now for one-cluster-at-a-time, it's a tradeoff.