MinIO AIops MCP server

<!-- mcp-name: io.github.AIops-tools/minio-aiops -->

MinIO AIops

Disclaimer: Community-maintained open-source project. Not affiliated with, endorsed by, or sponsored by MinIO, Inc. or any storage vendor. Product and trademark names belong to their owners. MIT licensed.

Governed AI-ops for MinIO object storage — for the homelab and small/medium self-hosted deployments where MinIO actually lives. Talks to the S3 API (official minio SDK, SigV4), the admin API (bucket quota, server info), the unauthenticated health endpoints (/minio/health/live|ready|cluster), and the cluster metrics endpoint (/minio/v2/metrics/cluster, bearer-token or public auth) — with a built-in governance harness: a unified audit log, a token/runaway budget guard, undo-token recording, and a descriptive risk tier on every audit row. Self-contained: no external skill-family dependency.

What it does

Four flagship analyses, plus the guarded reads and writes around them:

hotspots and imbalance → each finding as cause + suggested action (nearfull/full thresholds are named constants, not magic).

• capacityrca** — capacity vs used, offline drives/nodes, per-drive

anonymous/public policy statements (read and, far worse, write), missing default encryption, versioning off, no lifecycle.

• bucketexposureaudit — every bucket scored and ranked for

isn't: versioned buckets with no noncurrent expiry (old bytes accrue forever), incomplete multipart uploads with no abort rule (invisible space), large buckets with no lifecycle — with a clearly-labelled reclaimable estimate.

• lifecyclegapanalysis — the storage ILM should be reclaiming but

risk**: how many more drive failures each set can tolerate, which sets are healing, where heal errors are piling up.

• healinghealth — heal backlog and per-erasure-set write-quorum

capture the real prior state and record an undo descriptor; bucketdelete is refused unless the bucket is verifiably empty (including versions and delete markers) and removeincomplete_uploads only touches uploads older than a safety window.

• Governed writes. Bucket policy / versioning / lifecycle / quota changes

What works

check/status, capacity rca/usage, heal status/drives/nodes, bucket ls/info/objects/audit/ilm-gap/uploads plus guarded writes (bucket versioning-set/policy-set/lifecycle-set/quota-set/purge-uploads/delete), secret set/list/rm/migrate/rotate-password, mcp. Destructive commands take --dry-run and double-confirm.

• CLI (minio-aiops ...): init, overview, doctor, health

tools (29 read, 19 write), every one wrapped with the bundled @governedtool harness. The CLI is a convenience subset; the MCP surface is the whole tool. CLI writes delegate to the same governed functions, so they are audited identically.

• MCP server (minio-aiops mcp or minio-aiops-mcp): the full **48

~/.minio-aiops/secrets.enc (Fernet + scrypt) — never plaintext on disk. Unlock with a master password from MINIOAIOPSMASTER_PASSWORD (MCP/CI) or an interactive prompt (CLI).

• Encrypted credentials: the secret key lives in an encrypted store

MINIOPROMETHEUSAUTHTYPE=public are scraped directly; for the default (jwt) mode the bearer token is derived from the stored credentials** — no extra secret to manage.

• Metrics auth, both modes: servers running

inverse undo descriptor (prior policy JSON, prior lifecycle XML, prior versioning state, prior quota).

• Reversibility: reversible writes capture prior state and record an

Capability matrix (48 MCP tools)

Shortened. The full README is on GitHub.