cloudpin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDPIN_ENV | No | Use this environment (see Environments). An unknown name is an error. | |
| CLOUDPIN_NO_CACHE | No | Always ask the CLI instead of using the identity cache. | |
| CLOUDPIN_CACHE_DIR | No | Where the identity cache (and the time of the last update check) lives. | |
| CLOUDPIN_NO_UPDATE_CHECK | No | Never ask npm whether a newer cloudpin exists (NO_UPDATE_NOTIFIER works too). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
cloudpin keeps cloud CLIs (az, aws, gcloud, vercel, gh, kubectl, helm, supabase, wrangler) on the accounts .cloudpin.yml pins. Call cloudpin_status before cloud work. Before running any command that uses a cloud CLI, call cloudpin_check with the exact command line; run it only if the verdict is allow. On block or ask, stop and tell the user the reason and the fix. Never work around a block (another account, CLOUDPIN_SKIP, an environment variable, a script file). This server never runs or switches anything.
Switching accounts and editing .cloudpin.yml are the user's call. On a mismatch, cloudpin_switch_plan gives the commands for the user to run: show them, and never run them yourself. If this server may not be running in the project folder, pass it as cwd.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cloudpin_statusA | Which cloud accounts each CLI (az, aws, gcloud, vercel, gh, kubectl, helm, supabase, wrangler) is using here, what this project's .cloudpin.yml pins, which environment applies, and which agent hooks are installed. Call it before cloud work. |
| cloudpin_checkA | Would cloudpin allow this shell command, as an agent's? Returns each cloud CLI call in it, the account it would use and why, and the verdict (allow, block or ask) with the reason and the fix. Nothing is run. |
| cloudpin_doctorA | Why cloudpin may not be guarding here: cloudpin on PATH, shell wrappers, agent hooks missing or out of date, on Windows the PowerShell execution policy and PATH, the pin file, each CLI's account, each with its fix. Account IDs shortened. Nothing is changed. |
| cloudpin_switch_planA | On a mismatch with .cloudpin.yml: the exact commands that move each CLI to its pinned account, or what to do by hand, for the user to run. The same plan as cloudpin switch --json without --yes. Pinned IDs in full, those of the active login shortened. Nothing is run. Show the commands to the user and never run them yourself: switching accounts is the user's call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: status reports current accounts/pins/hooks, check evaluates a single shell command, doctor diagnoses why guarding is failing and offers fixes, and switch_plan emits remediation commands. The main overlap is between status and doctor, which both report account and hook state; only the 'diagnosis plus fix' framing separates them, so an agent could occasionally misselect.
All names share a consistent cloudpin_ prefix and lowercase snake_case formatting, which makes the set easy to group and scan. The suffixes mix grammatical forms (noun 'doctor'/'status', verb 'check', verb_noun 'switch_plan'), so the pattern is not a strict verb_noun convention, but it is still readable and predictable.
Four tools is well-scoped for a focused CLI account-guarding utility, and each covers a distinct facet of the workflow: inspect (status), evaluate (check), diagnose (doctor), remediate (switch_plan). No tool looks redundant or padded.
The read-only advisory surface is coherent and deliberately side-effect free, covering inspection, evaluation, diagnosis, and remediation planning. However, there is no way to read or edit the .cloudpin.yml pin file, initialize a pin file, or install/refresh agent hooks, so the lifecycle stops short of the write operations the domain implies.