Back to MCP Directory
Cyclops
Model Context Protocol moderate risk

Cyclops

Cyclops MCP enables AI agents to manage Kubernetes applications via high-level Cyclops Modules, abstracting complexity and ensuring production-ready deployments.

Connections & Capabilities

Connects To

GitHubKubernetes

Capabilities

readwrite

Quickstart

Config

{
  "mcpServers": {
    "mcp-cyclops": {
      "command": "mcp-cyclops"
    }
  }
}

Exposed MCP Tools (7)

moderate
create_module

Creates a new Cyclops Module in the Kubernetes cluster.

Creates Kubernetes resources, potentially impacting the cluster's state.

safe
get_module

Fetches a Cyclops Module by its name.

Read-only operation, no side effects.

safe
list_modules

Lists all Cyclops Modules in the cluster.

Read-only operation, no side effects.

high
update_module

Updates an existing Cyclops Module by its name.

Modifies existing Kubernetes resources, potentially disrupting running applications.

safe
get_template_schema

Returns the JSON schema for a given template.

Read-only operation, used for validation.

safe
get_template_store

Fetches a Template Store by Name

Read-only operation, no side effects.

safe
list_template_store

Lists Template Stores from cluster

Read-only operation, no side effects.

Safety Assessment

Cyclops MCP provides a layer of abstraction to manage Kubernetes resources, reducing the risk of misconfigurations. However, the ability to create, update, and delete modules means that a compromised or poorly configured agent could still cause significant damage. It is safe when used with a trusted agent and properly configured RBAC, but risky if exposed without proper authentication and authorization.

  • Uses high-level Cyclops Modules instead of direct Kubernetes resources.
  • Provides `get_template_schema` to validate values before creating modules.
  • Allows configuration via environment variables for added control.
  • Offers UI-based installation for simplified setup.
  • Allows creation, updating, and deletion of Kubernetes resources.
  • Requires careful configuration of KUBECONFIG and other environment variables.
  • Exposes the MCP server externally, potentially creating a security risk if not secured properly.
  • Relies on the agent's logic, which could lead to misconfigurations if flawed.