How to add Kom (Kubernetes Operations Manager) to Cursor

Multi-cluster Kubernetes MCP server with 59 tools for resources, pods, nodes, deployments and YAML. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 148★ · stdio · no auth

Cursor config for Kom (Kubernetes Operations Manager)

go build main.go

{
  "mcpServers": {
    "kom-kubernetes-operations-manager": {
      "command": "path/to/kom",
      "args": []
    }
  }
}

Setup steps

1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
2Paste the Kom (Kubernetes Operations Manager) config below into the "mcpServers" object.
3Fill in placeholder secrets, then save.
4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
5Ask Cursor to use one of Kom (Kubernetes Operations Manager)'s tools to confirm it's connected.

Before you start

A Kubernetes cluster and a kubeconfig (KUBECONFIG env var, defaults to ~/.kube/config)
Go toolchain to build the binary (go build main.go), or the embedded mcp.RunMCPServer call in a Go app
For SSE mode: network reachability to the server's :9096/sse endpoint

What Kom (Kubernetes Operations Manager) can do in Cursor

list_k8s_clusters

List all registered Kubernetes clusters.

restart_k8s_daemonset

Restart a DaemonSet by cluster, namespace and name.

scale_k8s_deployment

Scale a Deployment's replica count by cluster, namespace and name.

restart_k8s_deployment

Restart a Deployment by cluster, namespace and name.

stop_k8s_deployment

Stop a Deployment (set replicas to 0).

restore_k8s_deployment

Restore a Deployment's replica count.

update_k8s_deployment_image_tag

Update the container image tag of a Deployment.

get_k8s_deployment_rollout_history

Query a Deployment's rollout/upgrade history.

Security

These tools perform privileged, destructive cluster operations (delete resources, drain/cordon nodes, exec arbitrary commands in pods, apply/delete YAML, scale and roll back deployments). The server manages the cluster via the KUBECONFIG env var (defaults to ~/.kube/config) and has no built-in auth on the MCP layer. The SSE mode (http://IP:9096/sse) exposes these tools over the network with no authentication described in the README; restrict network access and run only against clusters you intend the AI client to control. AWS EKS credentials, when used, are held only in memory and cleared on restart.

Kom (Kubernetes Operations Manager) + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the Kom (Kubernetes Operations Manager) config there under the "mcpServers" key and restart the client.

Is Kom (Kubernetes Operations Manager) safe to use with Cursor?

Which transports does the MCP server support?

Both stdio and SSE. The compiled binary acts as a stdio server; running it also serves SSE at http://IP:9096/sse for private, multi-user deployments. Claude Desktop supports stdio only.

How many tools does it expose?

The README documents 59 MCP tools spanning cluster listing, dynamic resource CRUD (incl. CRDs), pod operations, node management, deployment lifecycle, storage/ingress classes, events, and YAML apply/delete.

How does it authenticate to Kubernetes?

It uses the KUBECONFIG environment variable (defaulting to ~/.kube/config) and supports registering multiple clusters, including AWS EKS via access key/secret/region. The MCP layer itself has no authentication described in the README.

View repo Full Kom (Kubernetes Operations Manager) page