MCP Devinfra MCP Server

MCP server that gives LLMs full control over local Kubernetes dev environments. Built in Go, it exposes 63 tools across 8 groups for managing k3d clusters, kubectl operations, Helm charts, Kustomize overlays, Tilt dev workflows, Artifact. The mcp devinfra mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

• k3d — (9 tools) — create, delete, start, stop, list clusters and nodes
• kubectl — (16 tools) — get, describe, apply, delete, logs, port-forward, raw command escape hatch
• Helm — (10 tools) — install, upgrade, uninstall, template, status, show values/chart, repo management (via Go SDK)
• Kustomize — (5 tools) — build, build-and-apply, edit image/namespace, list resources (via Go API)
• Tilt — (10 tools) — up, down, ci, logs, status, get, describe, trigger, session (queries via HTTP API)
• Artifact Hub — (6 tools) — search, package info, values, schema, readme, templates

Its toolset

Everything the assistant can do here goes through one of these:

• k3d — local Kubernetes clusters
• kubectl — cluster interaction
• tilt — dev workflow orchestration
• kubectl_logs — -follow is capped at 10 seconds
• Component — Integration
• Helm — Go SDK (helm.sh/helm/v3)
• Kustomize — Go API (sigs.k8s.io/kustomize/api)
• Field — Description
• kubeconfig — Path to kubeconfig (empty = default ~/.kube/config)
• default_context — Override kubeconfig current-context
• blocked_contexts — Glob patterns for contexts the safety layer will reject
• tilt_api — Tilt apiserver URL (empty = auto-discover from ~/.tilt-dev/config)

Adding it to your client

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

Configuration

• Go 1.26+ - Docker (for k3d clusters) - k3d — local Kubernetes clusters - kubectl — cluster interaction - tilt — dev workflow orchestration - Helm and Kustomize are optional at the CLI level (Go SDKs are embedded)

When to reach for it

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Devinfra's toolset — k3d, kubectl, tilt and 11 more — is a fair guide to whether it matches your workflow. It is maintained by remiphilippe; 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.

Caveats

• 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 MCP Devinfra.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp devinfra mcp server does with a few real requests.