Labsco
MCP SERVER

Cyclops MCP

by cyclops-ui ↗

Let an agent deploy to Kubernetes without touching raw YAML — it creates Cyclops Modules against your templates, and reads the template schema first so the values are valid.

Containers, Kubernetes & Cluster Operations
Summary
Schema-first is the guardrail, and it is built into the tool descriptions rather than left to the prompt.

An agent writing Kubernetes manifests directly has a large surface for silent mistakes; making it fetch the template schema and then fill a validated Module shrinks that to the fields the template actually accepts. The in-cluster SSE deployment is worth preferring over per-developer binaries — one server, one set of namespace settings, rather than everyone's local kubeconfig.

What it is

An MCP server for Cyclops, which sits over Kubernetes as a template layer. Instead of an agent editing Deployments, Services and Ingresses line by line, it creates and updates Cyclops Modules — high-level resources validated against a template's JSON schema. The workflow the tool descriptions enforce is to read the schema before writing, so misconfiguration is caught before it reaches the cluster.

What you get
  • Modules created and updated against a template, with the tool descriptions requiring a schema check first — `create_module`, `update_module`
  • The JSON schema for a template, which is what makes those values verifiable rather than guessed — `get_template_schema`
  • Existing modules listed and fetched by name — `list_modules`, `get_module`
  • Template stores listed and fetched by name, so an agent can see which templates the cluster offers — `list_template_store`, `get_template_store`
Requirements

A Kubernetes cluster with Cyclops and its CRDs installed — `modules.cyclops-ui.com`, `templateauthrules.cyclops-ui.com` and `templatestores.cyclops-ui.com` should be present. The easiest install is through the Cyclops UI under Addon > MCP server, which needs Cyclops v0.20.1 or greater; there is also a manifest to `kubectl apply` and a binary installable with `go install github.com/cyclops-ui/mcp-cyclops/cmd/mcp-cyclops@latest`. In-cluster, expose it with `kubectl port-forward -n cyclops svc/cyclops-mcp 8000:8000` and point the client at `http://localhost:8000/sse`. The binary connects with your `.kube/config` by default; `KUBECONFIG` and `CYCLOPS_KUBE_CONTEXT` override that, and `CYCLOPS_MODULE_NAMESPACE`, `CYCLOPS_HELM_RELEASE_NAMESPACE` and `CYCLOPS_MODULE_TARGET_NAMESPACE` place the resources it creates.

Setup effort

One command — GOBIN="$HOME/go/bin" go install github.com/cyclops-ui/mcp-cyclops/cmd/mcp-cyclops@latest