MCP Cyclops MCP Server

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. Exposed over MCP by the mcp cyclops mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

• 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

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need one environment variable: KUBECONFIG. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

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. MCP Cyclops's toolset — create_module, get_module, list_modules and 4 more — is a fair guide to whether it matches your workflow. It is maintained by cyclops-ui; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp cyclops mcp server does with a few real requests.