api_version
(optional): API version for the resource (e.g., 'v1', 'apps/v1')
How to use it
Project documentation lists api_version for the MCP Kubernetes Ro MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install MCP Kubernetes Ro
npx -y @patrickdappollonio/mcp-kubernetes-roOther tools in MCP Kubernetes Ro (21)
(optional): Container name (required for multi-container pods)
(optional): Kubernetes context to use (defaults to current context from kubeconfig)
(optional): Continue token for pagination (from previous response)
(required): Text data to encode
(optional): Field selector to filter resources (e.g., 'status.phase=Running')
(optional): Exclude lines matching these patterns (comma-separated). Works like grep -v - excludes lines containing any of these patterns
(optional): Include only lines matching these patterns (comma-separated). Works like grep - includes lines containing any of these patterns
(required): Port forward session ID (e.g., "pf-1")
(optional): Label selector to filter resources (e.g., 'app=nginx,version=1.0')
(optional): Maximum number of resources to return (defaults to all)
(optional): Maximum number of lines to retrieve
(required): Resource name
(optional): Target namespace (leave empty for cluster-scoped resources)
(optional): Specific node name to get metrics for. If not provided, returns metrics for all nodes.
(required): Pod name
(optional): Specific pod name to get metrics for. Requires namespace if specified.
(required): Array of port mappings, each with:
(optional): Return logs from the previous terminated container instance (like kubectl logs --previous)
(required): The type of resource to list - use plural form (e.g., 'pods', 'deployments', 'services')
(optional): Return logs newer than this time. Supports durations like "5m", "1h", "2h30m", "1d" or absolute times like "2023-01-01T10:00:00Z"
(optional): Whether to treat grep patterns as regular expressions instead of literal strings