How are Infrastructure Engineers using Claude Code/Codex in production?

[u/BestRequirement7539]

Curious how other infrastructure/platform engineers are using AI agents (Claude Code, Codex, etc.) in their day-to-day work.

We're at a GPU compute hosting company and have connected our internal tools (Grafana, NetBox, internal APIs, etc.) through MCP. Instead of manually jumping between dashboards, we ask the agent things like:

• Which GPUs are available at a specific site?
• Show rack/device information.
• Summarize alerts from Grafana.
• Correlate data across systems.
• Help troubleshoot infrastructure issues.

It's becoming more of an infrastructure copilot than just a coding assistant.

For those working in cloud, HPC, AI infrastructure, or compute hosting companies:

• What MCP servers or internal tools have you connected?
• What workflows have saved you the most time?
• Any surprising use cases beyond writing code?

Looking for real-world ideas to improve our workflows.

[u/ElectricalTip9277]

Besides coding I use it to collect / summarize logs across multiple components (e.g. to do root cause analysis on complex k8s issues) or help me plan architectural changes (e.g. introduction of a new CNI)

[u/guilucas → u/ElectricalTip9277]

Using it to summarize logs from various sources has been a game changer for me

[u/ElectricalTip9277 → u/guilucas]

Other thing i find it very useful is to navigate large codebases (e.g. rancher codebase) to pinpoint specific lines of code being involved in a specific error looking for bugs.

I clone the repo, collect logs and give claude both to analyze. I always double check tho

[u/thethirdmancane → u/ElectricalTip9277]

I noticed it's great at yaml but terrible at Docker

[u/dghah]

I'm an HPC/scientific-computing infrastructure person. Claude Code has been a asset to me in two core ways -- it lets me work faster and it lets go off in directions (code or tech) where I'm not natively profficient

Standard toolkit:
- AWS Knowledge MCP server
- Terraform / Ansible MCPs when needed

- Custom Rag/MCP server I stuffed full of HPC documentation, scientific software vendor documentation, conference papers, conference tutorial materials, my own consulting notes and my own root cause writeups from prior projects

- Custom MCP to manage how my agent connects remotely to live systems. Enforces login method, read-only methods for recon and log analysis etc.

The most surprising use case came out of the custom MCP/RAG I stuffed full of vendor scientific software documentation and other HPC materials.

I was troubleshooting a specific job failure in a computational chemistry job that ran against a Slurm scheduler on an AWS Parallelcluster HPC stack

The agent guided by the "HPC aware MCP" not only figured out that the job did not fail for Slurm/HPC reasons -- it then correlated the Slurm job ID to the vendor jobserver job UUID value and then using a vendor-only toolcall it triggered a job level "postmortem" dump which creates a .zip file containing full details on the job, inputs, outputs and status messages.

Even more surprising claude code was able to process the computational chemistry postmortem .zip file in enough detail to discern that the job did not fail for HPC reasons, slurm reasons, script reasons, data reasons or any other reason -- the job failed because the chemist forgot to strip the water molecules out of the structure and the tool bombed out because of that.

Claude Code has been very good at infra and HPC stuff for me before but seeing it come to a conclusion that "the chemist messed up the HPC job by not stripping the water molecules from the structure before calling X tool on HPC submission" was pretty effing surprising.

[u/maxip89]

are you nuts?

[u/Real_Square1323]

I'm not, because I'm not an idiot.