
Flux
STDIOConnect AI assistants to Kubernetes clusters with Flux Operator for GitOps troubleshooting
Connect AI assistants to Kubernetes clusters with Flux Operator for GitOps troubleshooting
The Flux MCP Server connects AI assistants directly to your Kubernetes clusters running Flux Operator, enabling GitOps analysis and troubleshooting through natural language.
Using AI assistants with the Flux MCP Server, you can:
Install the Flux MCP Server using Homebrew:
brew install controlplaneio-fluxcd/tap/flux-operator-mcp
For other installation options, refer to the installation guide.
Add the following configuration to your AI assistant's MCP settings:
{ "flux-operator-mcp":{ "command":"flux-operator-mcp", "args":[ "serve", "--read-only=false" ], "env":{ "KUBECONFIG":"/path/to/.kube/config" } } }
Replace /path/to/.kube/config
with the absolute path to your kubeconfig file,
you can find it with: echo $HOME/.kube/config
.
Copy the AI rules from instructions.md and place them into the appropriate file for your assistant.
Restart the AI assistant app and test the MCP Server with the following prompts:
For more information on how to use the MCP Server with Claude, Cursor, GitHub Copilot, and other assistants, please refer to the documentation website.
We welcome contributions to the Flux MCP Server project via GitHub pull requests. Please see the CONTRIBUTING guide for details on how to set up your development environment and start contributing to the project.
The MCP Server is open-source and part of the Flux Operator project licensed under the AGPL-3.0 license.