Lumino MCP Server

If you already use Lumino, the lumino mcp server is the piece that lets your assistant work with it directly. AI-powered SRE observability for Kubernetes/OpenShift with 40+ Tekton debugging tools.

What the server does

An open source MCP (Model Context Protocol) server empowering SREs with intelligent observability, predictive analytics, and AI-driven automation across Kubernetes, OpenShift, and Tekton environments.

LUMINO MCP Server transforms how Site Reliability Engineers (SREs) and DevOps teams interact with Kubernetes clusters. By exposing 39 specialized tools through the Model Context Protocol, it enables AI assistants to:

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• list_namespaces — List all namespaces in the cluster
• list_pods_in_namespace — List pods with status and placement info
• get_kubernetes_resource — Get any Kubernetes resource with flexible output
• search_resources_by_labels — Search resources across namespaces by labels
• query_kubearchive — Query archived Kubernetes resources from KubeArchive with optional log retrieval
• list_pipelineruns — List PipelineRuns with status and timing
• list_taskruns — List TaskRuns, optionally filtered by pipeline
• get_pipelinerun_logs — Retrieve pipeline logs with optional cleaning
• list_recent_pipeline_runs — Recent pipelines across all namespaces
• find_pipeline — Find pipelines by pattern matching
• get_tekton_pipeline_runs_status — Cluster-wide pipeline status summary
• analyze_logs — Extract error patterns from log text

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: PYTHONUNBUFFERED, THANOS_URL, PROMETHEUS_TOKEN, KUBERNETES_NAMESPACE, PROMETHEUS_URL, KUBEARCHIVE_HOST, OPENSHIFT_TOKEN, KUBERNETES_SERVICE_HOST. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Lumino's toolset — list_namespaces, list_pods_in_namespace, get_kubernetes_resource and 11 more — is a fair guide to whether it matches your workflow. It is maintained by geored; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Lumino.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.