kubeview-mcp
Enables management of Argo Workflows and Argo CD applications, including listing and inspecting workflows and applications via the Kubernetes API or CLI.
Allows inspection of Helm releases, including values, manifests, notes, hooks, status, and history, primarily via the Kubernetes API with CLI fallback.
Provides read-only tools to inspect, diagnose, and debug Kubernetes clusters, including listing/getting resources, fetching metrics, streaming logs and events, executing commands in containers, port-forwarding, and network diagnostics.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@kubeview-mcpshow me all pods in the default namespace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
KubeView MCP
Read-only Model Context Protocol server for Kubernetes diagnostics. Agents get two public tools, load schemas on demand, and run multi-step cluster workflows in a single execution pass — so Kubernetes, Helm, Argo Workflows, and Argo CD stay reachable without saturating the context window.
Background: Evicting MCP tool calls from your Kubernetes cluster
How it works
v2 publishes exactly two public tools: run_code and approval-gated kube_pod_exec. Everything else is discovered inside the sandbox via tools.list(), tools.search(), and tools.help() — progressive discovery + programmatic calling.
run_code executes bounded TypeScript with top-level await. One call can list workloads, correlate events, fetch logs, and diff Helm state without shipping intermediate payloads back through the model:
const pods = await tools.kubernetes.list({ namespace: 'payments' });
const unhealthy = pods.items.filter((p) => p.status?.phase !== 'Running');
return Promise.all(
unhealthy.map(async (pod) => ({
pod: pod.metadata?.name,
logs: await tools.kubernetes.logs({
namespace: 'payments',
podName: pod.metadata?.name,
tailLines: 100,
}),
})),
);Sensitive isolation —
kube_pod_execis unreachable from sandboxed code. Top-level exec requires MCP elicitation, is bound to the argument digest, expires after 10 minutes, and fails closed.kube_port_forwardis never a top-level tool and is denied inside code mode by default.tools.disabled()reports which policy blocked a capability and whether that denial is configurable.API-driven discovery — Argo Workflows and Argo CD are detected from the Kubernetes API, scoped to the active kube context, cached for 60 s. An unavailable optional API never blocks startup.
Native reads — resources, metrics, logs, events, and network probes go through the Kubernetes API. Helm releases are parsed from cluster Secrets or ConfigMaps; a local
helmbinary is a fallback, not a prerequisite.
Related MCP server: Kubernetes Tools MCP Server
Quick start
Prerequisites: Node.js ≥ 22 and access to a cluster (KUBECONFIG or in-cluster service account).
npx -y kubeview-mcp
# Claude Code
claude mcp add kubernetes -- npx kubeview-mcp{
"mcpServers": {
"kubeview": {
"command": "npx",
"args": ["-y", "kubeview-mcp"]
}
}
}In Cursor, /kubeview/code-mode injects the typed API into context.
Configuration
Cluster
Variable | Description | Default |
| Kubeconfig path |
|
| Kubernetes context; defaults to the active context | unset |
| Skip TLS verification for the Kubernetes API ( |
|
| Default operation timeout in ms | plugin default |
| Mask sensitive data globally |
|
| Disable the Kubernetes plugin ( | unset |
| Disable the Helm plugin ( | unset |
Mode and capabilities
Variable | Description | Default |
|
|
|
| Comma-separated code-mode denials; empty enables all | JSON/default |
| Argo override: |
|
| Argo CD override: |
|
|
|
|
| Force | unset |
HTTP transport
Variable | Description | Default |
|
|
|
| HTTP bind (when |
|
| Streamable HTTP endpoint path |
|
| Prefer JSON over SSE (drops mid-call notifications) |
|
| Host allowlist (required when binding to | local defaults |
| Origin allowlist for HTTP | unset |
| Shared 32+ byte signing secret; required for HTTP approvals | ephemeral (stdio) |
| Absolute shared-volume directory for one-time HTTP approvals | unset |
mkdir -p /tmp/kubeview-mcp-approvals
MCP_APPROVAL_STATE_SECRET='replace-with-at-least-32-random-bytes' \
MCP_APPROVAL_REPLAY_DIR=/tmp/kubeview-mcp-approvals \
MCP_TRANSPORT=http MCP_HTTP_HOST=127.0.0.1 MCP_HTTP_PORT=3000 npx -y kubeview-mcpEndpoint: http://127.0.0.1:3000/mcp. HTTP follows the MCP 2026-07-28 stateless core: a fresh server per request, no initialize, no Mcp-Session-Id. Each request carries protocol version, client identity, and capabilities in _meta; modern requests add Mcp-Method/Mcp-Name for gateway routing. 2025-era clients use the SDK's stateless fallback on the same endpoint. State that must survive across calls has to be passed as tool arguments or handles.
HTTP mode refuses to start without both approval variables. Multi-replica deployments need the same secret and a shared writable replay directory; the /tmp example is for a single process only. The published MCP registry entry still targets stdio.
Tool surfaces
| Exposed tools |
unset / |
|
|
|
Domain tools use an operation discriminator:
helm—list|get|debugargo—list|get|logs|cron_list(whenWorkfloworCronWorkflowis discoverable)argocd—list|get|resources|logs|history|status(whenApplicationis discoverable, or withARGOCD_SERVER+ARGOCD_AUTH_TOKEN)
Discovery is cached per kube context for 60 s. Missing optional APIs are omitted, not fatal.
Code mode
Code mode is the default (MCP_MODE=code). The agent writes short TypeScript against a typed tools global instead of calling dozens of MCP tools.
Inside run_code:
Typed
toolsnamespaces for Kubernetes, Helm, and any detected Argo capabilities, generated from live schemas so parameters cannot be hallucinated.Progressive discovery:
tools.list(),tools.search(),tools.help(), andtools.disabled()(the last reports why a capability was blocked).A locked-down runtime with only
consoleandtoolsin scope — no filesystem, no network, noprocess.
Capability | Inside | Top-level tool |
| Never available | Requires per-call user approval (10 min, argument-bound) |
| Denied by default (configurable) | Never exposed |
Everything else | Available | Only when |
Pod exec approval uses MCP elicitation and fails closed. The standalone npm run code-mode launcher has no trusted approval UI, so it always denies pod exec.
Customizing denials
MCP_CODE_MODE_DISABLED_TOOLS (comma-separated) controls which capabilities are blocked inside run_code. Resolution order:
MCP_CODE_MODE_DISABLED_TOOLSenv vardisabledToolsinkube-mcp.code-mode.jsonDefault:
["kube_port_forward"]
An empty env value clears the list. kube_pod_exec cannot be added — it is permanently blocked.
Protocol
MCP 2026-07-28:
JSON Schema 2020-12 in/out contracts with server-side validation
Machine-readable
structuredContentwith text fallbackAccurate
read-only,destructive,idempotent,open-worldannotationsDeterministic tool ordering with cache hints for fixed vs. discovery-dependent surfaces
Stateless HTTP with discovery and header-based routing (
Mcp-Method,Mcp-Name)Execution failures returned as tool errors; protocol errors reserved for malformed requests
Local development
git clone https://github.com/mikhae1/kubeview-mcp.git
cd kubeview-mcp && npm install
npm run build # compile
npm start # build + run
npm test # jest suite
npm run typecheck # tsc --noEmit
# Invoke a tool directly
npm run command -- kube_list --namespace=defaultProtocol tests pin the SDK v2 client to 2026-07-28 and route through the server handler in-process (no open ports):
npm test -- --runInBand \
tests/server/StreamableHttpTransport.integration.test.ts \
tests/server/StreamableHttpRuntime.test.ts \
tests/server/TransportConfig.test.ts \
tests/compat/McpSdkCompatibility.test.tsContributing
Contributions are welcome! Please feel free to submit an issue or a pull request.
License
MIT © mikhae1
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that provides safe, read-only access to Kubernetes resources for debugging and inspection. Built with security in mind, it offers comprehensive cluster visibility without modification capabilities.45MIT
- AlicenseAqualityCmaintenanceProvides a set of read-only Kubernetes functions via an MCP server, enabling interaction with Kubernetes clusters through agents or coding assistants like GitHub Copilot.93Apache 2.0
- FlicenseBqualityDmaintenanceA read-only Kubernetes MCP server that enables developers to inspect app status, view pod events, and fetch container logs from dev clusters without requiring full kubectl access.24
- AlicenseAqualityCmaintenanceA read-only MCP server for inspecting Kubernetes clusters, allowing LLMs to list resources, describe pods, and read logs without mutation.5MIT
Related MCP Connectors
The official MCP Server from Mia-Platform to interact with Mia-Platform Console
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
Read-only MCP server for ClassQuill, a tutoring-business-management platform.
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/mikhae1/kubeview-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server