Skip to main content
Glama
AmazingYe-oss

k8s-mcp-server

by AmazingYe-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

健康检查工具，返回 pong 表示服务器正常运行。

list_namespacesA

列出集群中所有 namespace 及其状态。

Args:
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"
list_podsA

列出指定 namespace 下的所有 pod 及其状态。

Args:
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"
    namespace: 指定的 namespace，默认 "default"
get_pod_logsA

获取指定 pod 的日志。

Args:
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"
    namespace: 指定的 namespace，默认 "default"
    pod_name: 指定的 pod 名称
    tail_lines: 返回最后多少行日志，默认 100
describe_podA

获取指定 pod 的详细信息，包括状态、IP、节点、容器状态、重启次数、镜像和资源配置。

Args:
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"
    namespace: 指定的 namespace，默认 "default"
    pod_name: 指定的 pod 名称
list_nodesA

列出集群中的所有节点及其状态、操作系统和 K8s 版本。

Args:
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"
list_eventsA

列出集群中所有 namespace 下的最近事件，按时间倒序排列，最多显示 20 条。

Args:
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"
diagnose_podA

诊断指定 Pod 的健康状态。

一次调用返回基本信息、容器状态、Warning 事件、日志和基于规则的初步诊断建议。

当用户需要排查 Pod 异常、崩溃、无法启动等问题时，优先使用此工具。

Args:
    namespace: Pod 所在的 namespace
    pod_name: Pod 名称
    cluster: 目标集群，可选 "local"（本地 k3s）或 "cloud"（阿里云 k3s），默认 "local"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

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

A4.3/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct resource or action: health check, namespaces, pods, logs, pod details, nodes, events, and a comprehensive diagnostic. The diagnose_pod tool is clearly positioned as a higher-level troubleshooting action, so there is no ambiguity.

Naming Consistency5/5

Tool names consistently follow the verb_noun pattern (list_*, get_*, describe_*, diagnose_*), with only 'ping' as a standard health-check verb. All names use lowercase with underscores, providing a predictable naming scheme.

Tool Count5/5

Eight tools is well within the ideal range for a focused Kubernetes inspection server. Each tool covers a distinct aspect of cluster and pod monitoring, and there is no redundancy or unnecessary bloat.

Completeness4/5

The tool set provides solid coverage for cluster health, namespace listing, pod logs, pod details, node information, events, and a diagnostic workflow. However, it lacks tools for other common Kubernetes resources like deployments, services, and configmaps, which would be expected from a general-purpose k8s server.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources