flux-operator

Overview

The Flux MCP Server is part of the Flux Operator project, which provides an 'Autopilot for Flux CD' by automating installation, configuration, and upgrades of Flux controllers. It connects AI assistants to Kubernetes clusters running the operator, enabling seamless interaction through natural language. The server acts as a bridge between AI tools and GitOps pipelines, allowing analysis of deployments across environments, troubleshooting issues, and performing operations using conversational prompts.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

• create_flux_instance

  Create or update a FluxInstance to install and configure Flux controllers

  Try:Create a Flux instance with kustomize-controller and helm-controllerTry:Update my Flux instance to version 2.3
• get_flux_report

  Retrieve the FluxReport to monitor deployment status and reconciler statistics

  Try:Show me the Flux deployment status reportTry:Check the reconciler statistics for the flux instance
• create_resource_set

  Create a ResourceSet to define a group of Flux and Kubernetes resources

  Try:Create a ResourceSet for my applicationTry:Define a new ResourceSet with parameters for my deployment
• sync_from_git

  Configure Flux to sync cluster state from a Git repository

  Try:Sync from my Git repository at https://github.com/my-org/my-fleet.gitTry:Set up Flux to pull from my Git repo main branch
• create_git_secret

  Create a Kubernetes secret for accessing private Git repositories

  Try:Create a Git secret for my private repositoryTry:Set up credentials for my GitHub repository
• get_flux_status

  Check the readiness status of Flux controllers

  Try:Is the flux controller ready?Try:Check the status of my Flux installation
• port_forward_flux_ui

  Port forward the Flux Web UI service for access

  Try:Forward the Flux UI to port 9080Try:Access the Flux Web UI
• configure_ephemeral_environment

  Set up ephemeral environments for pull request testing

  Try:Configure ephemeral environment for GitHub pull requestsTry:Set up a preview environment for GitLab merge requests
• apply_kustomize_patches

  Apply Kustomize patches to customize Flux controller deployments

  Try:Apply a node selector patch to my flux controllersTry:Add tolerations to the flux controllers
• get_reconciler_stats

  Retrieve statistics about Flux reconcilers

  Try:Show me the reconciler statisticsTry:Get details about the kustomize controller performance
• configure_cluster_sync

  Configure cluster synchronization from Git or container registries

  Try:Set up sync from my container registryTry:Configure flux to pull from S3 storage
• configure_flux_sharding

  Configure Flux controller sharding for multi-cluster deployments

  Try:Set up Flux sharding for my multi-tenant clusterTry:Configure flux with multiple controllers

Note: Tool names were inferred from the CRD names and configuration options mentioned in the README. The README mentions FluxInstance, FluxReport, and ResourceSet APIs but doesn't provide explicit MCP tool names. The tools are designed to interac

Comparable tools

Installation

helm install flux-operator oci://ghcr.io/controlplaneio-fluxcd/charts/flux-operator \
  --namespace flux-system

{
  "mcpServers": {
    "flux": {
      "command": "npx",
      "args": ["@fluxcd/mcp-server"]
    }
  }
}

FAQ

What is the Flux MCP Server?

The Flux MCP Server connects AI assistants to Kubernetes clusters running the Flux Operator, enabling natural language interaction with GitOps pipelines.

How does the Flux MCP Server integrate with existing workflows?

It extends the Flux Operator's capabilities, allowing AI assistants to analyze deployments, troubleshoot issues, and perform operations through conversational prompts while maintaining existing GitOps workflows.

Compare flux-operator with