mimiops-mcp
Provides integration with FluxCD to reconcile sources and HelmReleases, and to inspect reconciliation status and errors for GitOps-managed resources.
Allows inspecting Helm releases and rolling back a broken release to a previous working revision.
Provides tools for observing and safely managing Kubernetes workloads, including listing and describing pods, jobs, deployments, StatefulSets, DaemonSets, reading logs, and restarting workloads by deleting pods.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mimiops-mcplist pods in the default namespace and check for any CrashLoopBackOff"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Mimiops MCP Server
Motivation
There are many ways to manage Kubernetes workloads, but there are also many ways to break them by accident. We have already seen cases where AI agents did something that we did not expect. Giving an AI agent full access to Kubernetes can be risky, especially when it can create, update, or delete resources directly.
In my opinion, we need to provide safe and well-defined tools for AI agents. These tools should limit what an agent can do, validate changes before applying them, and help prevent dangerous operations.
We also need tools that can help investigate and fix workload issues. Many workloads are already managed by well-known tools such as Argo CD, FluxCD, Helm, and other GitOps or deployment systems. An AI agent should understand who manages a resource and avoid making direct changes that can conflict with these tools.
The goal is not to give AI full control of Kubernetes. The goal is to give AI a safe interface that allows it to understand problems, suggest changes, and perform only controlled operations.
Related MCP server: Kube MCP
Overview
Mimi OPS is not designed to give AI agents unrestricted Kubernetes access. Instead, it provides a small set of well-known and controlled operations.
The agent can observe, investigate, and perform a limited number of safe recovery actions. More dangerous operations, such as editing arbitrary resources, applying YAML, changing secrets, or deleting persistent data are strongly restricted.
This makes Mimi OPS an opinionated interface between AI agents and Kubernetes: powerful enough for common troubleshooting, but limited enough to reduce the risk of unexpected changes.
Kubernetes basic tools:
Pods
list — list pods and their current status.
get — get detailed information about a pod.
describe — inspect pod status, conditions, events, and related information.
logs — read container logs for troubleshooting.
delete — safely restart a workload by deleting a pod and allowing its controller to recreate it.
CronJobs and Jobs
list — list CronJobs and Jobs.
get — get information about a specific resource.
describe — inspect status, conditions, events, and failures.
Deployments, StatefulSets, and DaemonSets
list — list workloads and their current status.
get — get information about a specific workload.
describe — inspect replicas, rollout status, conditions, and related events.
Helm integration
Mimi OPS can inspect Helm-managed workloads and help recover them when a deployment fails:
list — list Helm releases.
describe — show release information, status, revision, and related resources.
rollback — roll back a release to a previous working revision when the current release is in a broken state.
FluxCD integration
Mimi OPS can work with FluxCD-managed resources without directly changing resources that are controlled by GitOps:
Reconcile Flux source resources to fetch the latest configuration.
Reconcile HelmRelease resources to retry or apply the expected Helm state.
Inspect reconciliation status and errors to understand why a deployment is not ready.
Installation
A Kubernetes MCP (Model Context Protocol) server written in Go. It exposes Kubernetes operations to MCP clients (Claude Desktop, Cursor, VS Code, etc.) over two transports:
mimiops-mcp mcp— stdio, for desktop MCP clients.mimiops-mcp server— HTTP/SSE, for web/remote MCP clients.
Running
Common flags
Flags are global (persistent) and accepted on both subcommands:
Flag | Default | Description |
| auto | Path to kubeconfig (defaults to |
| current-context | Kubernetes context to use |
| all namespaces | Scope operations to a namespace |
|
| Enable destructive tools (e.g. |
|
|
|
Per-command flags:
Command | Flag | Default | Description |
|
|
| HTTP/SSE listen port |
Examples
# stdio against a specific context
./bin/mimiops-mcp mcp --kubeconfig ~/.kube/dev.yaml --context prod-east
# SSE server scoped to a namespace, with destructive tools enabled
./bin/mimiops-mcp server --namespace default --allow-destructive --port 8080Development
make lint # golangci-lint
make unit # unit tests (build tag `unit`)
make test # lint + unit
make licenses # license audit (forbidden/restricted/unknown)
make docs # (Docker image docs targets are also available; see `make help`)Use make help for a full target list.
License
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive Kubernetes cluster management through kubectl operations, Helm chart deployments, pod troubleshooting, and node management. Supports both read-only and full cluster administration capabilities with built-in safety features.12,374MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with and manage Kubernetes clusters, supporting operations on pods, deployments, services, configmaps, secrets, namespaces, metrics, and events with built-in safety features for destructive actions.9141MIT
- AlicenseAqualityAmaintenanceEnables safe, read-only interaction with Kubernetes clusters, allowing users to list resources and fetch logs without any create/update/delete operations.116Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI agents to inspect and operate a Kubernetes cluster safely, with read-only mode and namespace allowlist for mutations.102MIT
Related MCP Connectors
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
The WAF for agents. Pattern-based + heuristic firewall scans prompts, RAG documents, tool argume...
See, price, and control every tool call your AI agents make: policy checks, cost, and audit tools.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sergelogvinov/mimiops-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server