● Community
glitternetwork
⚡ Instant
pinme
by glitternetwork · glitternetwork/pinme
Zero-config frontend deploys to IPFS via one CLI command — Claude runs pinme upload dist and hands back a preview URL.
PinMe is a CLI + Claude Skill that deploys static sites (dist/build/out/public) to IPFS in a single command, no accounts or servers. The skill contains an AI Execution Protocol so Claude knows exactly how to verify Node, install the CLI, detect the right build folder, and return the preview URL to the user.
Why use it
Key features
- One-command IPFS deploy — no account, no server setup
- Auto-detects build output folder (dist/, build/, out/, public/)
- AI Execution Protocol in the skill: verify Node → install → detect folder → deploy → return URL
- Returns a preview URL you can share immediately
- Works with any static site generator (Vite, Next export, Astro, SvelteKit static, etc.)
Live Demo
What it looks like in practice
pinme-skill.replay
▶ ready
Use Cases
Real-world ways to use pinme
When to use: You want to share a preview without configuring Vercel/Netlify, just a raw link.
Prerequisites
- Node.js installed — node >= 18 — the skill verifies this
- A built static site — Run your framework's build (e.g. npm run build)
Flow
-
Ask Claude to deploy
Build this Astro site and deploy it with pinme.✓ Copied
→ Claude runs the build, detects dist/, installs pinme if missing, runs the upload
-
Get the URL
(no prompt — just wait)✓ Copied
→ Preview URL returned in the chat
Outcome: A shareable IPFS-hosted preview.
Pitfalls
- Wrong folder detected (e.g. has both dist/ and build/) — Tell Claude explicitly: 'upload from build/'
- IPFS gateway slow on first load — Expected — subsequent loads are cached
When to use: You're iterating on a prototype and want every version to be linkable.
Flow
-
Build and deploy after each change
Every time I say 'ship', rebuild and upload via pinme, then post the URL.✓ Copied
→ Claude develops a rhythm of build → deploy → URL
Outcome: A linkable preview history of your iterations.
Pitfalls
- IPFS CIDs change on every deploy (expected) — Use ENS or DNSLink if you want a stable URL
Combinations
Pair with other MCPs for X10 leverage
Claude writes or edits the site, then deploys via pinme without leaving the session
Edit the hero copy, rebuild, then pinme upload dist — give me the new URL.✓ Copied
Commit the change and ship a preview URL in one turn
Commit the change on a branch, deploy via pinme, and put the preview URL in the PR description.✓ Copied
Cost & Limits
What this costs to run
- API quota
- PinMe free tier with usage caps; check pinme.eth for current limits
- Tokens per call
- Trivial — the skill is small
- Monetary
- Free tier available; paid tiers for larger / more persistent pins
- Tip
- Let test previews expire; only pin the production URL long-term.
Security
Permissions, secrets, blast radius
Credential storage: No credentials required for anonymous uploads. Optional account key for pinning persistence.
Data egress: Uploaded bundle goes to IPFS — public by design. Never upload secrets, .env files, or non-public assets.
- IPFS content is PUBLIC — anything in the uploaded folder is globally readable.
Troubleshooting
Common errors and fixes
pinme: command not found
The skill should install it; run npm i -g pinme manually if blocked.
Verify: pinme --version
Upload hangs
Check network; some corporate firewalls block IPFS bootstrap nodes.
Wrong folder uploaded
Pass an explicit path: pinme upload ./dist rather than relying on auto-detect.
Alternatives
pinme vs others
| Alternative | When to use it instead | Tradeoff |
|---|
| Vercel / Netlify | You want custom domains, serverless functions, or CI integration | More features, requires account and config |
| GitHub Pages | Your code is on GitHub and you want a stable github.io URL | Coupled to a repo; slower deploy loop |