Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
cloudpin
Overview
Description from the maker (original English)
Read-only checks that cloud CLI commands run on the accounts a project pins in .cloudpin.yml.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cloudpin": {
"command": "npx",
"args": [
"-y",
"cloudpin",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add cloudpin -- npx -y cloudpin mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cloudpin": {
"command": "npx",
"args": [
"-y",
"cloudpin",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"cloudpin": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cloudpin",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account paureis, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32505 servers in this category
- Published to the registry more recently than 95% of the other 32505 servers in this category
- Basic checks equal to or better than 100% of the other 32505 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is cloudpin safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.2.3) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
topo^alpin
by topoalpin.app
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
cloudpin
Pin cloud accounts to a project, and stop any command (yours or your AI agent's) that would run on the wrong one.
az, aws, gcloud, vercel, gh, kubectl, helm, supabase and wrangler act on whichever account, cluster or project you used last. With a work account, a personal one and a client or two on the same machine, sooner or later something gets deployed to, or deleted from, the wrong place. Coding agents make it more likely: they run these commands for you and never stop to ask which account is active. cloudpin checks before the command runs.
Install
pnpm add --global cloudpinOn macOS and Linux, Homebrew works too, from paureis/homebrew-tap (it runs on Homebrew's own Node.js, installed if it isn't there yet):
brew install paureis/tap/cloudpinOn Windows, Scoop works too, from paureis/scoop-bucket. It installs Scoop's own Node.js (nodejs-lts) if needed, and cloudpin always runs on that one. A global install (scoop install -g) needs nodejs-lts installed globally too. nodejs-lts puts its folders at the front of your user PATH, so in new shells node and npm are Scoop's (and npm install --global installs there), ahead of any other Node.js on your user PATH; one on the system PATH, where the nodejs.org installer puts it, still comes first. Uninstalling nodejs-lts breaks cloudpin until you run scoop install nodejs-lts again, and Scoop's no_junction setting isn't supported.
scoop bucket add paureis https://github.com/paureis/scoop-bucketscoop install paureis/cloudpin
Without Node.js at all, each release from 1.3.0 has a standalone cloudpin.exe for 64-bit Windows: unzip cloudpin-X.Y.Z-win-x64.zip from Releases into a folder on your PATH. It carries its own Node.js, so a Node.js security fix reaches it only in a new cloudpin. winget (winget install paureis.cloudpin) comes with 1.3.0 too.
npm, Yarn, Bun, or no install
npm install --global cloudpinyarn global add cloudpin bun add --global cloudpin
try it without installing
npx cloudpin --help
Requires Node.js 22 or later. Works on Windows, macOS and Linux. The .cloudpin.yml format is stable from 1.0 on (see Configuration), and feedback is very welcome.
Latest release: 1.2.3 (2026-11-05): two security fixes since 1.2.1, please upgrade. 1.2.1 (2026-10-29): agent hooks now find calls hidden by heredocs in $( ), run-time values, PowerShell syntax and wrappers such as xargs, sudo, npx or cmd /c, and gcloud checks the impersonated account; please upgrade. 1.2.0 (2026-10-29) was run it everywhere. A GitHub Action (paureis/cloudpin-action) checks the accounts before a deploy job, built on the new cloudpin check --only and --json; Homebrew and Scoop installs; the MCP server for every agent, listed in the official MCP Registry (docs/mcp.md); Codex and Copilot CLI hooks that PowerShell's execution policy can't stop on Windows; and fixes to which Vercel team and Wrangler account a command uses. See the CHANGELOG. 1.1 added the Claude Code plugin, and 1.0 made the .cloudpin.yml format stable.
Quick start
cd your-projectcloudpin init # pin the accounts you are logged into now cloudpin install-hook claude # protect your AI agent (or codex, cursor, copilot, antigravity, gemini) echo 'eval "$(cloudpin shell-init bash)"' >> ~/.bashrc # protect your terminal
Commit .cloudpin.yml so everyone on the project gets the same protection. cloudpin status shows each CLI's active account next to what is pinned. To see a block without risking anything, pin a wrong account in a scratch folder (edit an ID in .cloudpin.yml) and run a read-only command such as gh repo list.
To undo it all: cloudpin uninstall-hook claude, remove the shell-init line from your profile, and delete .cloudpin.yml. The only other things cloudpin writes are a short-lived identity cache in your user cache folder, .git/cloudpin-env if you ran cloudpin use, and *.cloudpin-backup copies next to agent settings it edited.
Usage
# Write .cloudpin.yml from the accounts you are logged into nowcloudpin init
...or add them as one environment of the file (see Environments)
cloudpin init --env production --protected
Show the environments, or choose the one to use in this clone
cloudpin use [ | --clear]
Check every pinned account; exit 1 on a mismatch (handy in CI and scripts)
cloudpin check
Check only these clouds; each must be pinned, installed and logged in to the pinned
account, so a CLI missing on the runner fails, not skipped. --json prints an overall "result" (match,
mismatch, unpinned or error) and each cloud's status, reason and fix. Exit codes stay the same.
cloudpin check --only azure,aws [--json]
Switch each pinned CLI to its pinned account: shows the plan, asks once (--yes: don't ask), runs the CLIs' own switch
commands, then checks again; exit 1 unless everything matches. What it won't do (a login, supabase link, a Wrangler
config edit, an overriding variable) it names for you. --json: the plan, what ran and the check after.
cloudpin switch [--yes] [--json] [--only ]
See each CLI's active account, what this folder pins, and which agent hooks are installed (--json for tools)
cloudpin status
Why was a command blocked, or would it be? See the pin, the account it would use, and the verdict, without
running it. One quoted argument is read as a full line; --agent shows what an agent hook decides; --json for tools.
cloudpin explain -- vercel deploy --prod cloudpin explain "cd ../web && vercel deploy"
Something looks off? Check the whole setup and get the fix for each problem; exit 1 if anything fails.
--json shortens account IDs and hides your home folder, so it is safe to paste in a bug report.
cloudpin doctor [--json]
Run one command only if it would act on the pinned account; exit 3 if blocked
cloudpin exec -- vercel deploy --prod
Shell functions that route az, aws, gcloud, vercel, gh, kubectl, helm, supabase and wrangler through cloudpin
cloudpin shell-init bash|zsh|pwsh
Add or remove the hook in an agent's settings (this project, or yours with --user)
cloudpin install-hook [--user] cloudpin uninstall-hook [--user]
How it works
A .cloudpin.yml in your project lists the accounts it uses. cloudpin init writes it for you, with readable names as comments:
azure:subscription: "3f2a0000-0000-0000-0000-000000000c91" # Acme Prod tenant: "8b1d0000-0000-0000-0000-00000000044e" aws: account: "123456789012" gcloud: account: "deploy@acme.com" project: "acme-prod" vercel: team: "team_x9KqZr" # acme github: user: "acme-bot" kubernetes: server: "https://acme-prod.hcp.westeurope.azmk8s.io:443" # acme-prod-admin namespace: "payments" supabase: project: "abcdefghijklmnopqrst" # Acme prod org: "acme" cloudflare: account: "0123456789abcdef0123456789abcdef" # Acme
Before a guarded command runs, cloudpin works out which account that command would use (asking the CLI, or for Kubernetes reading the kubeconfig), honouring the command's own flags and environment, and compares the answer with the file:
| CLI | What is pinned | What cloudpin takes into account |
|---|---|---|
az | subscription ID, tenant ID | --subscription, AZURE_CONFIG_DIR |
aws | account ID | --profile, AWS_PROFILE, access key variables, SSO |
gcloud | account, project | --account, --project, --configuration, --impersonate-service-account, --access-token-file, CLOUDSDK_* |
vercel / vc | team ID | --scope, --team, --token, VERCEL_TOKEN, VERCEL_ORG_ID, linked project (.vercel/project.json or a repository's .vercel/repo.json) |
gh | user, host | --hostname, GH_HOST, GH_TOKEN, GITHUB_TOKEN |
supabase | project ref, organisation (optional) | --project-ref, SUPABASE_PROJECT_ID, the project supabase link saved, --workdir, SUPABASE_WORKDIR, --profile, SUPABASE_ACCESS_TOKEN |
wrangler (Cloudflare) | account ID | account_id in wrangler.json, wrangler.jsonc or wrangler.toml (and its [env.NAME] with --env / CLOUDFLARE_ENV), --config, --cwd, CLOUDFLARE_ACCOUNT_ID, the project's account cache, the credentials' only account |
kubectl, helm | API server URL, namespace (optional) | --kubeconfig, KUBECONFIG, --context, --cluster, --server, -n, -A, kuberc; helm's --kube-context, --kube-apiserver, HELM_* |
For Kubernetes the server URL is pinned rather than the context name, because context names are personal: the same cluster is prod on one laptop and acme-prod-admin on another. init writes your context name as a comment, and pins the namespace only if your context sets one. With a namespace pinned, -A / --all-namespaces is a mismatch. Commands that never reach a cluster (kubectl config, kubectl kustomize, helm template, helm repo, ...) are never blocked, and standalone kustomize isn't guarded at all. cloudpin can't see a namespace: written inside a manifest you apply, so pin the namespace and keep manifests namespace-free if that matters to you.
For gcloud, an impersonated service account (the last one in a delegation chain) is the account compared with the pin; with an access token or token file the account can't be known, so an account pin gives "can't tell".
For Supabase the project ref is worked out the way the CLI does it, without a network call: --project-ref, then SUPABASE_PROJECT_ID, then the project supabase link saved in supabase/.temp/. A linked branch counts as its parent project. The organisation comes from supabase projects list. The local stack (start, stop, status, functions serve, and db reset, db diff or migration up without --linked) is never blocked. A --db-url pointing anywhere but your own machine is stopped, because cloudpin can't tell which project a URL belongs to.
For Cloudflare, cloudpin follows Wrangler's order: account_id in the config file Wrangler would find, then CLOUDFLARE_ACCOUNT_ID, then the account Wrangler cached, then the only account the login sees (wrangler whoami --json), with the auth profile the command uses (--profile or wrangler auth activate). Variables Wrangler loads from the project's .env files count too. If it sees several and none is set, Wrangler would ask or fail, so cloudpin stops the command, as for a profile it can't ask about. Local commands (dev, and d1, kv key or r2 object without --remote) are never blocked; dev with remote: true bindings reaches your account unchecked. Built to Wrangler's source and docs,
Only the beginning is shown; read the rest in the repo