Skip to content

The infra plugin and CLI ​

Everything Claude Code on my Mac knows about this stack comes from one plugin, infra, published from the stu-greenshoots/infra repo (marketplace stu-infra).

What's in it ​

PartWhat it does
Coolify MCP serverConnects Claude to https://coolify.stu-bot.uk/mcp. The auth headers come from infra mcp-headers, so the secrets stay in ~/.config/infra/secrets.env
infra CLIAdded to the PATH. Covers what Coolify's MCP doesn't: netcup power and snapshots, DNS, R2 usage, SSH
reference/platform.mdThe rules every app follows (see Deploying an app)
Skillsonboard, deploy, data, bus, box, claude-job

The skills ​

SkillUsed when I ask to...
infra:onboardput a project on the box for the first time
infra:deploydeploy, check status, read logs, restart or roll back
infra:dataadd a database, set up or check backups, restore
infra:bussend or receive messages between services
infra:boxdo anything with the server itself: health, snapshots, power, firewall
infra:claude-jobhand a task to Claude on the server

The CLI ​

Python with only the standard library, so it runs on any Mac with python3. It reads ~/.config/infra/secrets.env and never prints a secret. Every command is listed on the Commands page.

Secrets file ​

~/.config/infra/secrets.env, chmod 600, one KEY='value' per line. It holds the Coolify token, the Cloudflare tokens and IDs, the R2 keys, the Access service token, the netcup refresh token, the Telegram bot token, the runner token and the Claude token. It's never committed. Moving to a new Mac means copying it across by hand.

Updating the plugin ​

Push changes to the repo, then:

sh
claude plugin marketplace update stu-infra