pulsemcp scanned Safe content atomic mcp-remote

Cyclops

Cyclops MCP server provides AI assistants with safe Kubernetes application management through high-level abstractions, enabling creation and updates of applications using validated templates rather than direct manipulation of low-level Kubernetes resources. Built in Go using the cyclops-ui/cyclops framework, the implementation offers tools for managing Cyclops Modules (template-based application definitions), Template Stores (collections of Helm/Git/OCI templates), and retrieving JSON schemas for template validation, with comprehensive CRUD operations including module creation, updates, resource listing, and manifest generation. The server validates all module configurations against template schemas before deployment and integrates with Kubernetes through the Cyclops controller, serving DevOps teams who want to give AI agents controlled access to application deployment without risking direct cluster manipulation, and organizations seeking to abstract Kubernetes complexity from both developers and AI systems while maintaining production safety through template-driven workflows.

Cognium trust score

65%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.

Scan details: Circle-IR · 2026-09-02 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/cyclops-ui/mcp-cyclops
Author type: human
Last scanned: 2026-09-02
Updated: 2026-09-02

View source Find related skills

MCP

Resolve Cyclops from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"