Name: Dev/Infra
Author: remiphilippe

LABSCO SUMMARY

The safety layer is the reason to use this rather than a shell.

Applies default to a dry run, contexts can be blocked by pattern, and the raw escape hatch is checked against a denylist. That is what makes handing an agent a cluster different from handing it a terminal.

What it is

A Go server for local Kubernetes development; its README counts 63 tools across eight groups: k3d clusters, kubectl operations, Helm charts, Kustomize overlays, Tilt workflows, Artifact Hub lookups, documentation search and composite CI routines. Helm and Kustomize run through their Go SDKs rather than the command line; kubectl, k3d and Tilt's lifecycle commands shell out.

What you get

k3d clusters and their nodes created, started, stopped, listed and deleted
kubectl work — get, describe, apply, delete, logs, port-forward — plus a raw escape hatch for anything the sixteen typed tools do not cover (kubectl_apply, kubectl_logs, kubectl_raw)
Helm installs, upgrades, uninstalls, templating, status, values and repository management through the Helm Go SDK — ten tools (helm_install, helm_upgrade)
Kustomize overlays built, built and applied, and edited for image or namespace — five tools
Tilt brought up and down, run in CI mode, and queried for status, logs, session and resource detail over its HTTP API — ten tools
Artifact Hub searched for packages, values, schemas, readmes and templates, with an optional automatic lookup before an install — six tools
Full-text search over a bundled Bleve index of the tilt, k3d, kubectl and Helm documentation, 257+ pages of it
Composite routines that bootstrap an environment, tear it down, or collect diagnostics — three tools
Eight prompts for the multi-step jobs — bootstrap_dev_env, debug_pod, deploy_and_verify, cluster_health_check, ci_run and more — and read-only resources for cluster info, namespaces, pods, services, deployments, events, Tilt status, kubeconfig, Helm releases and doc pages

Requirements

Go 1.26 or newer to build, plus Docker, k3d, kubectl and tilt on the machine; Helm and Kustomize command-line tools are optional because their Go SDKs are embedded. It inherits your own kubeconfig and cluster credentials, and runs over stdio or with --http. Configuration is a JSON file with no comments allowed. Three safety behaviours are worth knowing before you wire it up: kubectl_apply defaults to dry_run: "client" so a real apply has to be asked for explicitly, blocked_contexts rejects operations against contexts matching patterns such as production or staging-*, and kubectl_raw is checked against a denylist that only unsafe: true overrides.

Setup effort

Build from source — git clone https://github.com/remiphilippe/mcp-devinfra.git

See installation options

USE CASES

01

Applying a manifest without doing it for real first

The apply runs as a client-side dry run unless you ask otherwise, so the diff and the validation errors come back before anything changes. Turning it into a real apply is a deliberate argument, not a default.

kubectl_apply

02

Reading why a pod will not start

Describe the pod, pull its logs and read the recent events in the namespace, in one pass. The debug_pod prompt does exactly this sequence when you would rather not spell it out.

kubectl_logs

03

Installing a chart with values that exist

Look the chart up on Artifact Hub first and read its actual values and schema, then install. An automatic lookup before install can be turned on so this happens whether or not you remember.

helm_installhelm_upgrade

04

Keeping production out of reach of a dev tool

Add glob patterns to the blocked contexts list and the safety layer refuses operations against anything matching, whatever the current kubeconfig context happens to be. This is the setting worth doing on day one.

kubectl_raw

05

Standing up a whole dev environment from scratch

One composite routine creates the k3d cluster, merges the kubeconfig, applies the Kustomize overlay and starts Tilt. The matching teardown reverses it, so an environment is cheap enough to throw away.

06

Looking up syntax instead of guessing at it

Search the bundled tilt, k3d, kubectl and Helm documentation from inside the session. The index ships with the server, so the answer does not depend on a search engine or on what the model remembers.

63 tools

Listed in project docs. Your client may show a different list.

`k3d_cluster_create`

Create a new k3d cluster

BEFORE YOU INSTALL

What to know first

Tools you get

63 tools named in the project's documentation.

Requires

Go 1.26+
Docker

INSTALLATION

Connect your client

Server setup

TERMINAL

git clone https://github.com/remiphilippe/mcp-devinfra.git
cd mcp-devinfra
make build

MCP Clients

Claude Code, Claude Desktop, Cursor

JSON

{
  "mcpServers": {
    "devinfra-mcp": {
      "command": "devinfra-mcp",
      "args": [
        "--config",
        "<YOUR_PATH_TO_SETTINGS>"
      ]
    }
  }
}

make build puts the binary at bin/devinfra-mcp inside your clone, not on your PATH: use its full path as "command" (or copy it onto your PATH). --config is optional — it points at a JSON file that overrides the defaults (no comments allowed); drop both arguments to run with defaults.

Codex

CODEX · TOML

[mcp_servers.devinfra-mcp]
command = "devinfra-mcp"
args = ["--config", "<YOUR_PATH_TO_SETTINGS>"]

make build puts the binary at bin/devinfra-mcp inside your clone, not on your PATH: use its full path as "command" (or copy it onto your PATH). --config is optional — it points at a JSON file that overrides the defaults (no comments allowed); drop both arguments to run with defaults.

HTTP server

HTTP SERVER · TERMINAL

./bin/devinfra-mcp --http --addr :8080 --config settings.json

Dev/Infra

The safety layer is the reason to use this rather than a shell.

What it is

What you get

Requirements

Setup effort

Applying a manifest without doing it for real first

Reading why a pod will not start

Installing a chart with values that exist

Keeping production out of reach of a dev tool

Standing up a whole dev environment from scratch

Looking up syntax instead of guessing at it

63 tools

k3d_cluster_create

k3d_cluster_delete

k3d_cluster_list

k3d_cluster_start

k3d_cluster_stop

k3d_node_list

k3d_kubeconfig_get

k3d_registry_create

k3d_image_import

kubectl_get

kubectl_apply

kubectl_delete

kubectl_describe

kubectl_logs

kubectl_exec

kubectl_port_forward

kubectl_rollout_status

kubectl_patch

kubectl_create_namespace

kubectl_config_view

kubectl_cluster_info

kubectl_top

kubectl_events

kubectl_wait

kubectl_raw

helm_repo_add

helm_repo_update

helm_install

helm_upgrade

helm_uninstall

helm_list

helm_template

helm_status

helm_show_values

helm_show_chart

kustomize_build

kustomize_build_and_apply

kustomize_edit_image

kustomize_edit_namespace

kustomize_list_resources

tilt_up

tilt_down

tilt_ci

tilt_logs

tilt_args

tilt_status

tilt_trigger

tilt_get

tilt_describe

tilt_session

artifacthub_search

artifacthub_get_package

artifacthub_get_values

artifacthub_get_schema

artifacthub_get_readme

artifacthub_get_templates

doc_search

doc_search_rebuild

doc_get

doc_list_topics

ci_bootstrap

ci_teardown

ci_diagnostics

What to know first

Tools you get

Requires

Connect your client

`k3d_cluster_create`

`k3d_cluster_delete`

`k3d_cluster_list`

`k3d_cluster_start`

`k3d_cluster_stop`

`k3d_node_list`

`k3d_kubeconfig_get`

`k3d_registry_create`

`k3d_image_import`

`kubectl_get`

`kubectl_apply`

`kubectl_delete`

`kubectl_describe`

`kubectl_logs`

`kubectl_exec`

`kubectl_port_forward`

`kubectl_rollout_status`

`kubectl_patch`

`kubectl_create_namespace`

`kubectl_config_view`

`kubectl_cluster_info`

`kubectl_top`

`kubectl_events`

`kubectl_wait`

`kubectl_raw`

`helm_repo_add`

`helm_repo_update`

`helm_install`

`helm_upgrade`

`helm_uninstall`

`helm_list`

`helm_template`

`helm_status`

`helm_show_values`

`helm_show_chart`

`kustomize_build`

`kustomize_build_and_apply`

`kustomize_edit_image`

`kustomize_edit_namespace`

`kustomize_list_resources`

`tilt_up`

`tilt_down`

`tilt_ci`

`tilt_logs`

`tilt_args`

`tilt_status`

`tilt_trigger`

`tilt_get`

`tilt_describe`

`tilt_session`

`artifacthub_search`

`artifacthub_get_package`

`artifacthub_get_values`

`artifacthub_get_schema`

`artifacthub_get_readme`

`artifacthub_get_templates`

`doc_search`

`doc_search_rebuild`

`doc_get`

`doc_list_topics`

`ci_bootstrap`

`ci_teardown`

`ci_diagnostics`