mcp-capi

The server exposes powerful Cluster API operations and sensitive information (like workload cluster kubeconfigs) via the Model Context Protocol. While the core implementation uses well-vetted Kubernetes client libraries and includes input validation for CLI parameters, secure deployment is critical. HTTP-based transports (SSE, Streamable HTTP) open network listeners. If exposed publicly without strong authentication and authorization, this could lead to unauthorized cluster management, configuration changes, or sensitive data disclosure. The self-update mechanism fetches from a trusted GitHub repository, but without explicit signature verification, it introduces a potential, albeit low, risk if the repository were compromised. Some tools are currently placeholders and would require further security review upon full implementation.