Lumino Mcp Server

Created By
spre-sre4 months ago
Overview

what is Lumino MCP Server?

Lumino MCP Server is an open-source Model Context Protocol (MCP) server designed to enhance the capabilities of Site Reliability Engineers (SREs) and DevOps teams by providing intelligent observability, predictive analytics, and AI-driven automation for Kubernetes, OpenShift, and Tekton environments.

how to use Lumino MCP Server?

To use Lumino MCP Server, clone the repository from GitHub, install the required Python dependencies, and configure the MCP client to connect to the server. Users can interact with the server through natural language queries to monitor and analyze their Kubernetes clusters.

key features of Lumino MCP Server?

  • Real-time monitoring of cluster health and resources.
  • Automated root cause analysis for failed pipelines.
  • Predictive analytics for resource bottlenecks and potential issues.
  • Simulation of configuration changes to assess impact before deployment.
  • Advanced log analysis and event intelligence.

use cases of Lumino MCP Server?

  1. Monitoring Kubernetes cluster health and resource usage.
  2. Analyzing logs and events for troubleshooting.
  3. Predicting resource bottlenecks before they impact services.
  4. Simulating changes to configurations for risk assessment.
  5. Generating reports for CI/CD pipeline performance.

FAQ from Lumino MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows AI assistants to interact with various tools and services in a standardized way.

  • Is Lumino MCP Server free to use?

Yes! Lumino MCP Server is open-source and free to use.

  • What are the prerequisites for running Lumino MCP Server?

You need Python 3.10 or higher and access to a Kubernetes or OpenShift cluster.

Server Config

{
  "mcpServers": {
    "lumino": {
      "type": "stdio",
      "command": "./.venv/bin/python",
      "args": [
        "./main.py"
      ],
      "env": {
        "PYTHONUNBUFFERED": "1"
      }
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
spre-sre
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago