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.
This server publishes no instructions, or was last inspected before Glama recorded them.
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. |
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 2 tools
cloudpin_status reports current cloud account/environment/hook context, while cloudpin_check evaluates a proposed shell command. They are mostly distinct, though both discuss per-CLI account usage and could be momentarily confused as a preflight vs. status check.
Both tools consistently use the cloudpin_ prefix followed by a short lowercase identifier. The pattern is predictable and readable despite status being a noun and check being noun/verb-like.
The server has only two tools, which feels thin even for a narrow guardrail/inspection purpose. Each earns its place, but the surface could reasonably support more operations such as managing pins or hooks.
The pair covers inspecting context and checking commands, but there are notable gaps: no tool to modify .cloudpin.yml pins, manage environment selection, or install/configure the agent hooks mentioned in cloudpin_status. The core read/check workflow exists but lifecycle operations are missing.