rootcause

What is RootCause?

RootCause is a local-first MCP server that helps operators manage Kubernetes resources and identify the real root cause of failures through interoperable toolsets. It runs as a fast, single-binary stdio MCP server built in Go, designed for use with MCP clients like Claude Desktop, VS Code (GitHub Copilot), and Codex CLI.

How to use RootCause?

Install the binary via Homebrew, curl, or Go install, then run it with a config file (--config config.toml). RootCause uses your existing kubeconfig for authentication. Connect any MCP client (e.g., Claude Desktop, Copilot) by pointing it to the RootCause command with stdio transport. Optional flags enable read-only mode, disable destructive operations, or select specific toolchains.

Key features of RootCause

• Local-first: uses your kubeconfig only, no API keys
• Interoperable toolchains: K8s, Linkerd, Istio, Karpenter, Helm, AWS
• Fast, portable single Go binary (stdin/stdout MCP transport)
• Built-in structured debugging with root cause, evidence, and next checks
• Plugin-ready SDK to add toolchains without duplicating K8s logic
• Safety modes: read-only and disable-destructive flags

Use cases of RootCause

• Diagnose Kubernetes failures with automated root cause analysis
• Manage clusters across toolchains (K8s, Linkerd, Istio, Helm, AWS) from one MCP server
• Provide read-only debugging access to production clusters via safety modes
• Integrate failure detection into AI coding assistants (Claude, Copilot, Codex)

FAQ from RootCause

How does RootCause differ from other Kubernetes MCP servers?

RootCause is local-first (no API keys), uses a fast Go binary instead of npx, and offers interoperable toolchains for Linkerd, Istio, Karpenter, Helm, and AWS alongside core Kubernetes tools.

What platforms and models does RootCause support?

RootCause supports macOS, Linux, and Windows. It works with any MCP client that uses stdio transport.

Does RootCause require a cloud API key or in-cluster deployment?

No. Phase 1 uses only your local kubeconfig identity. In-cluster deployment is intentionally out of scope for this version. AWS IAM tools use the standard credential chain.

What are the known limitations of RootCause?

RootCause uses MCP over stdio only; HTTP/SSE is not implemented in Phase 1. Config reload requires SIGHUP (not supported on Windows—restart the process).

What is the pricing/licensing model of RootCause?

The README does not specify a license or pricing. It is hosted on GitHub as a public repository; users are asked to star the repo to support growth.