Overview

The Komodor AI SRE MCP Server exposes Klaudia's cluster visibility, health analysis, cost insights, and investigation/remediation capabilities as MCP tools - so engineers can work with Klaudia directly from any MCP-compatible client (Codex, Cursor, Claude, or an internal agent platform) instead of switching to the UI or Slack. This lets teams embed Klaudia into their own developer workflows and agentic tooling while preserving the same RBAC and data boundaries as the rest of Komodor.

Note: The MCP Server is currently in beta. Contact your Komodor CSM to have it enabled for your account.

How it works

Each tool call runs under the identity and RBAC of the authenticated user - Klaudia only surfaces data and actions that user is already entitled to in Komodor.

Connecting: Point your MCP-compatible client at the Komodor MCP Server endpoint:

https://mcp.komodor.com/mcp

OAuth process: 

• When you connect an MCP client (e.g. Codex) to the Komodor MCP Server, the client opens a browser consent screen
• Choose Allow Access. 
• Once allowed, your client holds a token scoped to your own Komodor identity, which it presents on each request - so every tool call runs under your existing RBAC, the same as if you were using the Komodor UI directly.

Available tools

Cluster & Service Visibility

• whoami - Confirms the authenticated Komodor identity and verifies the connection.
• get_clusters - Lists all Kubernetes clusters accessible in the Komodor workspace.
• get_services_by - Searches workloads/services by cluster, namespace, kind, or health status.
• get_service_yaml - Retrieves the full manifest for a workload (Deployment, DaemonSet, StatefulSet, Rollout).

Health & Cost

• get_health_risks - Lists health risks, violations, and misconfigurations across clusters/namespaces.
• get_health_risk_data - Retrieves detailed analysis for a specific health risk by ID.
• get_cost_right_sizing_per_service - Service-level right-sizing recommendations and potential savings.
• get_cost_right_sizing_per_container - Container-level CPU/memory right-sizing recommendations.

Investigation & Remediation

• trigger_klaudia_rca - Starts an automated Klaudia root-cause analysis on a Kubernetes resource.
• get_klaudia_rca_results - Checks RCA progress and retrieves the final analysis.
• ask_klaudia - Starts or continues a Klaudia chat session for infrastructure questions, investigation, or remediation guidance.
• get_klaudia_chat_result - Polls a chat session until it completes, fails, or pauses (and flags if a session appears stalled).
• respond_klaudia_chat - Responds to a paused chat (e.g., approving/rejecting a suggested action, selecting an option).
• upload_klaudia_attachment - Uploads a file or image for Klaudia to use within a chat session.

When to use it

• Working inside a coding agent - When you're already in Codex, Cursor, or a similar tool, you can trigger a Klaudia RCA or ask a question about your cluster without leaving your editor.
• Embedding Klaudia into internal platforms - Point your own developer portal, chatbot, or internal agent at the MCP Server to give your engineers Klaudia's investigation and remediation capabilities inside tools they already use.