Custom Resource Definition Crd Querying

via “custom resource definition (crd) querying”

Model Context Protocol (MCP) server for Kubernetes and OpenShift

Unique: Uses Kubernetes dynamic client to support arbitrary CRDs without hardcoding resource types, enabling agents to query application-specific resources (service mesh, operators, etc.) through a unified MCP interface

vs others: More flexible than hardcoded resource types; supports any CRD without code changes; integrates custom resource querying into agent workflows without requiring separate API clients per CRD

via “custom resource definition (crd) operations with dynamic schema support”

** Provides multi-cluster Kubernetes management and operations using MCP, It can be integrated as an SDK into your own project and includes nearly 50 built-in tools covering common DevOps and development scenarios. Supports both standard and CRD resources.

Unique: Uses Kubernetes discovery API to automatically detect CRD schemas at runtime, enabling fluent API operations on any CRD without code generation or pre-built typed clients; transparently handles API group/version resolution via discovery cache

vs others: Eliminates the need for client-go code generation per CRD, which typically requires 100+ lines of generated code per CRD; more flexible than typed clients because new CRDs can be managed without recompilation