The Cyclops MCP(模型上下文协议) MCP server is a publicly available project. Review the upstream repository for installation instructions, supported tools, compatibility, permissions, and current maintenance status.
Configuration
Configuration, transport, authentication, and runtime requirements vary by project. Open the repository before connecting and use the smallest set of credentials and permissions required.
Context7 Platform - Up-to-date Code Docs For Any Prompt
upstash
Community
Context7 MCP server providing up-to-date, version-specific documentation and code examples for libraries, enabling coding agents to fetch accurate docs and code snippets. Requires an API key for higher rate limits, passed via CONTEXT7_API_KEY header.
57.7Kstars0forks
Playwright MCP
Microsoft Corporation
Community
A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. Enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.
35.5Kstars0forks
AIHawk
feder-cr
Community
AIHawk is an anti detect browser and web browsing agent, open source, with an MCP server for coding agents: undetected, no captchas, no blocks. It requires an OpenRouter API key for the standalone web UI mode, which can be provided via the --openrouter-key flag or the OPENROUTER_API_KEY environment variable or a .env file in the running directory.
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.
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
Install via UI
The easiest way to install the Cyclops MCP server is through the Cyclops UI. Below are instructions on how to install it via binary and kubectl, but the recommended way of installing it is via the UI.
⚠️ To install Cyclops MCP through the UI, you should run Cyclops on a version v0.20.1 or greater
Install the Cyclops MCP by going to sidebar “Addon” > "MCP server". You can now click "Install Cyclops MCP server" and your Cyclops MCP server will be up and running in a few seconds.
Now that your MCP server is up running, all thats left is exposing it outside of your cluster and connecting your AI agent to it.
To expose the MCP server on localhost you can simply port-forward it with the following command:
To connect it to an AI agent you will just have to provide the Cyclops MCP server in its configuration. For example, to add it to Cursor, you can simply add it with the following JSON:
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.
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
Install to a Kubernetes cluster manually
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