homelab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOMELAB_MCP_CONTEXT | No | kubeconfig context to use | current-context |
| HOMELAB_MCP_READONLY | No | 1/true disables all mutating tools | 0 |
| HOMELAB_MCP_MAX_REPLICAS | No | Upper bound for scale_deployment | 10 |
| HOMELAB_MCP_MUTABLE_NAMESPACES | No | Namespaces mutations may touch; * = all | default,apps,monitoring,ci |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cluster_summaryA | Node and pod health totals plus the list of unhealthy pods. Start here. |
| list_podsB | List pods (optionally one namespace). Unhealthy pods sort first. |
| list_deploymentsC | List deployments with ready/desired replica counts. |
| list_eventsB | Recent cluster events; Warning-type events sort first. |
| pod_logsC | Tail a pod's logs. |
| node_healthA | Per-node readiness, kubelet version, capacity, and pressure conditions. |
| restart_deploymentC | Rollout-restart a deployment (subject to the mutable-namespace allowlist). |
| scale_deploymentB | Scale a deployment to N replicas (0..max), subject to the allowlist. |
| delete_podA | Delete a pod so its controller recreates it (subject to the allowlist). |
| server_infoA | Report the effective configuration (context, read-only, allowlist). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Michael-WhiteCapData/WhiteCapData-Dev'
If you have feedback or need assistance with the MCP directory API, please join our Discord server