mcpnertes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPNERTES_CONFIG | No | Path to a configuration TOML file. If set, it is used instead of './config.toml' or the default package config. | |
| MCPNERTES_NAMESPACE_DENY | No | Comma-separated list of namespaces to deny. Defaults to empty. | |
| MCPNERTES_RESOURCE_BLOCK | No | Comma-separated list of resource kinds to block. Case-insensitive. Defaults to 'Secret'. | Secret |
| MCPNERTES_NAMESPACE_ALLOW | No | Comma-separated list of allowed namespaces, '*' allows all. Defaults to '*'. | * |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_deploymentsA | List all deployments in a specified namespace |
| get_eventsB | Get Kubernetes events from the cluster for a specific namespace or all namespaces |
| get_logsB | Get logs from pods, deployments, jobs, or resources matching a label selector |
| list_namespacesA | List all namespaces in the cluster (filtered by the namespace allowlist) |
| list_nodesA | List all nodes in the cluster |
| list_podsA | List all pods in a namespace or across all namespaces |
| get_pod_logsB | Get logs from a pod in a specified namespace |
| list_resourceA | List resources of any kind (including CRDs) via the dynamic client. GET/LIST only; never mutates. Blocked kinds (see config.toml) are refused. |
| get_resourceA | Get a single resource of any kind (including CRDs) by name via the dynamic client. GET only; never mutates. Blocked kinds are refused. |
| list_api_resourcesA | Discover which resource kinds (including CRDs) the cluster exposes and can be listed. Read-only discovery; blocked kinds are omitted. |
| list_servicesA | List all services in a namespace or across all namespaces |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
There is notable overlap between list_pods, list_deployments, list_services, list_resource, and list_api_resources. list_resource and get_resource are generic dynamic-client tools that can overlap with the specific resource listers, though the specific ones are convenient. get_pod_logs and get_logs also overlap, with get_logs being a broader version of get_pod_logs.
Most tools follow a consistent list_<resource> or get_<resource> pattern. Minor deviations: list_resource and get_resource are generic rather than resource-specific, and list_api_resources is a discovery operation rather than listing actual resources, but the overall pattern is predictable.
11 tools is a reasonable count for a Kubernetes MCP server covering common read-only operations. It is slightly redundant because generic list_resource/get_resource could subsume the specific listers, but the count is not excessive.
The server is read-only by design, so it covers listing and getting resources, logs, events, and discovery. However, it lacks common read operations like describe/status for resources, and there is no way to get a single deployment or pod by name except through the generic get_resource, which is a minor gap.