Kubeview MCP Server

Read-only MCP server enabling code-driven AI analysis of Kubernetes clusters

Remote serverstreamable-httpTypeScript

What is the Kubeview MCP MCP server?

Read-only MCP server enabling code-driven AI analysis of Kubernetes clusters. That is what the kubeview mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Add to your mcpServers config (Cursor, Claude Desktop, etc.):

The tools it exposes

The server publishes 6 tools. What each one is for:

  • Prerequisites — The Prerequisites tool exposed by this server
  • Installation — The Installation tool exposed by this server
  • Kubernetes — The Kubernetes tool exposed by this server
  • Helm — The Helm tool exposed by this server
  • Argo — The Argo tool exposed by this server
  • Utilities — The Utilities tool exposed by this server

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: MCP_MODE, MCP_HTTP_HOST, MCP_HTTP_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js ≥ 18 - Access to a Kubernetes cluster - Optional CLIs in $PATH: helm (fallback only), argo, argocd

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Kubeview MCP's toolset — Prerequisites, Installation, Kubernetes and 3 more — is a fair guide to whether it matches your workflow. It is maintained by mikhae1; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Kubeview MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
InstallationThe Installation tool exposed by this server.
KubernetesThe Kubernetes tool exposed by this server.
HelmThe Helm tool exposed by this server.
ArgoThe Argo tool exposed by this server.
UtilitiesThe Utilities tool exposed by this server.

How to install the Kubeview MCP MCP server

{
  "mcpServers": {
    "kubeview": {
      "command": "npx",
      "args": ["-y", "kubeview-mcp"],
      "env": {
        "MCP_MODE": "your-value",
        "MCP_HTTP_HOST": "your-value",
        "MCP_HTTP_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js ≥ 18 - Access to a Kubernetes cluster - Optional CLIs in $PATH: helm (fallback only), argo, argocd
VariableDescriptionRequired
MCP_MODEConfiguration value read at startup.Optional
MCP_HTTP_HOSTEndpoint or connection string the server talks to.Optional
MCP_HTTP_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Kubeview MCP to Prerequisites.
  • Use Kubeview MCP to Installation.
  • Use Kubeview MCP to Kubernetes.

Frequently asked questions

It connects Kubeview MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Prerequisites, Installation, Kubernetes, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Kubeview MCP directly.