MCP.so
ログイン

Cyclops MCP (MCP)

@cyclops-ui

基本情報

カテゴリ

その他

トランスポート

stdio

作者

cyclops-ui

Cyclops MCP について

Model Context Protocol server for Cyclops

#kubernetes#devops#mcp#cyclops#platform-engineering#mcp-server

Cyclops MCP の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Cyclops MCP のツール

7

Create new Module. Before calling this tool, make sure to call `get_template_schema` to validate values for the given template

Fetch Module by name

List all Cyclops Modules

Update Module by Name. Before calling this tool, make sure to call `get_template_schema` to validate values for the given template

Returns JSON schema for the given template. Needs to be checked before calling `create_module` tool

Fetch Template Store by Name

List Template Stores from cluster

概要

What is Cyclops MCP?

Cyclops MCP (Model Context Protocol) allows AI agents to manage Kubernetes applications by creating and updating Cyclops Modules safely. It abstracts low‑level Kubernetes resources (Deployments, Services, Ingresses) so agents work with high‑level templates and schemas, reducing misconfigurations.

How to use Cyclops MCP?

Install Cyclops MCP via the Cyclops UI (sidebar Addon → MCP server) or by deploying its binary or manifest to your cluster. Expose the server (e.g., kubectl port-forward -n cyclops svc/cyclops-mcp 8000:8000), then add its URL (e.g., http://localhost:8000/sse) to your AI agent’s MCP configuration.

Key features of Cyclops MCP

  • Create new Cyclops Modules from validated templates
  • List and fetch existing Modules by name
  • Update Modules with schema‑validated values
  • Retrieve JSON schema for any available template
  • List and fetch Template Stores from the cluster
  • Configure via environment variables (kubeconfig, context, namespaces)

Use cases of Cyclops MCP

  • Let AI agents provision production‑ready applications without touching raw YAML
  • Safely update existing Kubernetes applications through high‑level Modules
  • Abstract Kubernetes complexity from both developers and AI agents
  • Enable rapid iteration while preventing uncaught misconfigurations

よくある質問

1

What is the difference between creating a Module and editing low‑level Kubernetes resources?

Cyclops MCP creates Cyclops Modules — high‑level resources that abstract Deployments, Services, and Ingresses. The agent first validates values against the template schema, reducing the risk of misconfigurations.

2

What are the runtime dependencies of Cyclops MCP?

Cyclops MCP requires Cyclops (version `v0.20.1` or greater for UI install) and its CRDs to be installed in the Kubernetes cluster. It uses the in‑cluster config or `$HOME/.kube/config` by default.

3

Where does Cyclops MCP store data?

The server creates and manages Cyclops Modules and Template Stores inside the target Kubernetes cluster. Namespaces for modules, Helm releases, and target resources are configurable via environment variables.

4

What transport types does Cyclops MCP support?

Cyclops MCP supports both stdin (via the `mcp-cyclops` binary) and SSE (Server‑Sent Events, deployed as a service in the cluster). The UI install method deploys an SSE server.

5

How do I configure the Cyclops MCP server for a different Kubernetes context?

Set the `KUBECONFIG` environment variable to the path of your kubeconfig file and optionally set `CYCLOPS_KUBE_CONTEXT` to the desired context. Other configurable variables control module and Helm release namespaces.

コメント

「その他」の他のコンテンツ