Schema | Kube MCP

Kube MCP

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`KUBEMCP_CONFIG_SOURCE`	No	Configuration source: 'local' or 'custom'	local
`KUBEMCP_KUBECONFIG_PATH`	No	Custom kubeconfig path
`KUBEMCP_RESPONSE_FORMAT`	No	Response format: 'json', 'toon', or 'auto'	auto
`KUBEMCP_DEFAULT_NAMESPACE`	No	Default namespace	default

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

Name	Description
k8s_deploymentsA	Manage Kubernetes deployments. Actions: list: List all deployments in a namespace get: Get deployment details scale: Scale deployment replicas (requires confirm=true or dryRun=true) restart: Perform rolling restart (requires confirm=true or dryRun=true) get_status: Get rollout status get_metrics: Get aggregated metrics for a deployment
k8s_podsA	Manage Kubernetes pods. Actions: list: List pods in a namespace with optional label selector get: Get pod details delete: Delete a pod (requires confirm=true or dryRun=true) get_logs: Get logs with filtering (severity, grep, time-based) get_status: Get detailed pod status summarize_logs: Get log summary statistics (90%+ token reduction)
k8s_servicesC	Manage Kubernetes services. Actions: list: List all services in a namespace get: Get service details get_endpoints: Get endpoints for a service
k8s_configmapsA	Manage Kubernetes ConfigMaps. Actions: list: List all ConfigMaps in a namespace get: Get a specific ConfigMap create: Create a new ConfigMap update: Update an existing ConfigMap (requires confirm=true or dryRun=true) delete: Delete a ConfigMap (requires confirm=true or dryRun=true)
k8s_secretsA	Manage Kubernetes Secrets. Actions: list: List all Secrets in a namespace get: Get a specific Secret (metadata only, no data) create: Create a new Secret update: Update an existing Secret (requires confirm=true or dryRun=true) delete: Delete a Secret (requires confirm=true or dryRun=true)
k8s_namespacesA	Manage Kubernetes namespaces. Actions: list: List all namespaces in the cluster get: Get details of a specific namespace create: Create a new namespace delete: Delete a namespace (requires confirm=true or dryRun=true)
k8s_metricsB	Get Kubernetes resource metrics (CPU/Memory). Actions: get_pod_metrics: Get resource metrics for pods get_node_metrics: Get resource metrics for nodes
k8s_eventsB	Get Kubernetes cluster events. Actions: list: Get cluster events with optional filtering get_resource: Get events for a specific resource get_recent: Get recent events sorted by timestamp
k8s_auditB	Manage audit logging and safety controls. Actions: get_status: Check dry-run mode and session stats set_dry_run: Enable/disable dry-run mode globally get_session_log: View changes made in this session get_stats: Get statistics about operations in this session clear_session: Clear session audit log configure: Update audit settings (requireConfirmation, logToConsole)

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored 2026-04-18 07:00 across 9 tools

Disambiguation5/5

Each tool targets a distinct Kubernetes resource type (e.g., configmaps, deployments, pods) with clear boundaries. The actions within each tool are well-defined for that resource, preventing overlap or confusion between tools. An agent can easily distinguish between managing pods versus deployments versus services.

Naming Consistency5/5

All tool names follow a consistent 'k8s_' prefix with the resource name (e.g., k8s_configmaps, k8s_deployments). Actions within tools use consistent verbs like list, get, create, update, delete. This predictable pattern enhances readability and usability across the entire set.

Tool Count5/5

With 9 tools covering core Kubernetes resources (configmaps, deployments, events, metrics, namespaces, pods, secrets, services, plus audit), this is well-scoped for a Kubernetes management server. Each tool serves a distinct purpose, and the count aligns with typical MCP server ranges (3-15 tools).

Completeness4/5

The tool set provides comprehensive CRUD/lifecycle coverage for key Kubernetes resources, including audit features. Minor gaps exist, such as no update/delete for services or events, but core operations are covered. Agents can handle most Kubernetes management tasks without dead ends.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers