FluxCD MCP Server

Flux MCP Server

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:

• Debug GitOps pipelines end-to-end from Flux resources to application logs
• Get intelligent root cause analysis for failed deployments
• Compare Flux configurations and Kubernetes resources between clusters
• Visualize Flux dependencies with diagrams generated from the cluster state
• Instruct Flux to perform operations using conversational prompts

Quickstart

Install the Flux MCP Server using Homebrew:

For other installation options, refer to the installation guide.

Add the following configuration to your AI assistant's MCP settings:

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:

• "Which cluster contexts are available in my kubeconfig?"
• "What version of Flux is running in my current cluster?"

For more information on how to use the MCP Server with Claude, Cursor, GitHub Copilot, and other assistants, please refer to the documentation website.

Documentation

• Flux MCP Server Overview
• Installation Guide
• Transport Modes and Security Configurations
• Effective Prompting Guide
• MCP Tools Reference
• MCP Prompts Reference

Contributing

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.

License

The MCP Server is open-source and part of the Flux Operator project licensed under the AGPL-3.0 license.