Cyclops MCP allows your favorite AI agent to manage your Kubernetes applications. Cyclops MCP servers provide tools for agents to create and update existing applications safely.
mcp-server-demo.mp4
This means it can check all of your existing templates and the schema of those templates to create accurate and production-ready applications. Your agent now has much less room to make a misconfiguration since it creates high-level resources (Cyclops Modules) instead of touching every line of your Kubernetes resources (Deployments, Services, and Ingresses).
It allows you to move fast and ensure no uncaught misconfigurations are hitting your production.
With Cyclops and our MCP, you can now abstract Kubernetes complexity from your developers AND your AI agents
Check our docs on how it install it with a single command - https://cyclops-ui.com/docs/installation/install/manifest
You can download the Cyclops MCP server binary with the following command:
GOBIN="$HOME/go/bin" go install github.com/cyclops-ui/mcp-cyclops/cmd/mcp-cyclops@latest
⚠️ By default, Cyclops MCP will use the.kube/configfile to connect to your cluster
Configure your MCP Cyclops server:
{
"mcpServers": {
"mcp-cyclops": {
"command": "mcp-cyclops"
}
}
}Instead of having each developer install mcp-cyclops binary, you can install the Cyclops MCP server with SSE as transport type to your Kubernetes cluster and allow all of your developers to connect to the same server.
-
Before installing, make sure Cyclops and all its CRDs are installed in your cluster:
-
Check Cyclops pods are running:
kubectl get pods -n cyclops
Should write:
NAME READY STATUS RESTARTS AGE cyclops-ctrl-676b5d9789-ntcls 1/1 Running 0 94s cyclops-ui-7798655f97-xdg29 1/1 Running 0 94s -
Check if CRDs are installed
kubectl get crds | grep cyclops-uiShould write:
modules.cyclops-ui.com 2025-04-26T15:28:18Z templateauthrules.cyclops-ui.com 2025-04-26T15:28:18Z templatestores.cyclops-ui.com 2025-04-26T15:28:18Z
-
-
Install Cyclops MCP server with the following command:
kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/mcp-cyclops/refs/heads/main/install/mcp-server.yaml
-
You can now expose the
cyclops-mcpservice. To test your MCP server, you can port-forward it:kubectl port-forward svc/cyclops-mcp -n cyclops 8000:8000
-
Add your Cyclops MCP server host, or in case you are testing it, the localhost address where you port-forwarded the MCP service:
{ "mcpServers": { "mcp-cyclops": { "url": "http://localhost:8000/sse" } } }
| Tool | Description |
|---|---|
create_module |
Create new Module. Before calling this tool, make sure to call get_template_schema to validate values for the given template |
get_module |
Fetch Module by name |
list_modules |
List all Cyclops Modules |
update_module |
Update Module by Name. Before calling this tool, make sure to call get_template_schema to validate values for the given template |
get_template_schema |
Returns JSON schema for the given template. Needs to be checked before calling create_module tool |
get_template_store |
Fetch Template Store by Name |
list_template_store |
List Template Stores from cluster |
You can configure Cyclops MCP server via env variables. Below is an example of adding the configuration for specifying the kubeconfig file the Cyclops MCP server should use when managing your Cyclops applications.
{
"mcpServers": {
"mcp-cyclops": {
"command": "mcp-cyclops",
"env": {
"KUBECONFIG": "/path/to/your/kubeconfig"
}
}
}
}
Below is the list of environment variables used for configuring your Cyclops MCP server:
| Env var | Description |
|---|---|
KUBECONFIG |
Path to kubeconfig file (optional, defaults to in-cluster config or $HOME/.kube/config) |
CYCLOPS_KUBE_CONTEXT |
Kubernetes context to use (optional) |
CYCLOPS_MODULE_NAMESPACE |
Namespace where modules are stored |
CYCLOPS_HELM_RELEASE_NAMESPACE |
Namespace for Helm releases |
CYCLOPS_MODULE_TARGET_NAMESPACE |
Target namespace for modules |