k8s-dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| K8S_CONTEXT_CACHE | No | Cache directory for cloned repos (default: ~/.cache/k8s-dev-mcp) | ~/.cache/k8s-dev-mcp |
| K8S_CONTEXT_CONFIG | No | Path to a custom config.yaml |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-kepsB | List Kubernetes Enhancement Proposals. Filter by SIG name, status, or search query. |
| read-kepB | Read the full KEP design document (README.md) by its number. |
| read-kep-metadataA | Read kep.yaml metadata: status, milestones, feature gates, authors. |
| list-docsA | List available Kubernetes convention and guideline documents. |
| read-docA | Read a Kubernetes convention/guideline document, optionally a specific section. |
| list-doc-sectionsB | List section headings in a document. |
| search-k8s-docsA | Full-text search across all configured Kubernetes repos (enhancements, community, website). |
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 7 tools
Each tool targets a distinct operation: listing vs reading vs searching, and documents vs KEPs vs metadata. There is no overlap or ambiguity.
Tools follow a verb-noun pattern with hyphens (list-, read-, search-). Minor inconsistencies like plural 'docs' vs singular 'doc' and use of 'k8s' abbreviation exist, but overall pattern is clear.
7 tools is well-scoped for the domain of Kubernetes documentation and KEPs, covering listing, reading, searching, and metadata access without bloat.
The tool set covers the full range of expected operations for a read-only documentation server: listing, reading, searching, and retrieving metadata. No obvious gaps.