kubeview-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MODE | No | Server mode: all, code, or tools | all |
| KUBECONFIG | No | Path to kubeconfig file | ~/.kube/config |
| MCP_HTTP_HOST | No | HTTP bind host when MCP_TRANSPORT=http | 127.0.0.1 |
| MCP_HTTP_PATH | No | Streamable HTTP endpoint path | /mcp |
| MCP_HTTP_PORT | No | HTTP port when MCP_TRANSPORT=http | 3000 |
| MCP_LOG_LEVEL | No | Log level: error, warn, info, debug | info |
| MCP_TRANSPORT | No | Transport: stdio (default) or http | stdio |
| MCP_ALLOWED_HOSTS | No | Comma-separated Host allowlist for HTTP mode | local defaults |
| MCP_HIDE_SENSITIVE | No | Mask sensitive data globally | false |
| MCP_HTTP_STATELESS | No | Disable session IDs in HTTP mode | false |
| MCP_ALLOWED_ORIGINS | No | Comma-separated Origin allowlist for HTTP mode | |
| MCP_HTTP_JSON_RESPONSE | No | Prefer JSON responses over SSE | false |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_codeA | Execute bounded TypeScript with top-level await against progressively discovered Kubernetes capabilities. Use tools.list(), tools.search(), tools.help(), and typed namespaces; inspect tools.disabled() for policy denials. Return a value from the script. Full documentation and types are available through the code-mode prompt and file:///sys/global.d.ts. |
| kube_pod_execA | Execute a command in a container of a pod via the Kubernetes API (no kubectl). Captures stdout/stderr and returns them when the command completes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code-mode | TypeScript API documentation for the run_code environment. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Global Type Definitions |
TDQS
Scored across 2 tools
run_code and kube_pod_exec have clearly distinct purposes: one executes TypeScript scripts against Kubernetes APIs, the other runs commands inside pod containers. There is no functional overlap, so agents should not confuse them.
Both names follow a verb_noun pattern, but their styles diverge: run_code uses a bare verb and object, while kube_pod_exec uses a kube_ prefix and a more specific compound noun. This inconsistency is minor but noticeable.
With only two tools, the server is on the thin side. However, one tool is a flexible code-execution interface, so the count might be acceptable for a narrow, specialized scope.
The server is named kubeview, yet there are no viewing or resource-list tools. run_code can potentially interact with Kubernetes capabilities, but it does not provide a direct, discoverable surface for typical read operations, leaving significant gaps for a toolset claiming to be a Kubernetes viewer.