● Comunidad
glitternetwork
⚡ Instantáneo
pinme
por 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.
Por qué usarlo
Características clave
- 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.)
Demo en vivo
Cómo se ve en la práctica
pinme-skill.replay
▶ listo
Casos de uso
Usos del mundo real: pinme
Cuándo usarlo: You want to share a preview without configuring Vercel/Netlify, just a raw link.
Requisitos previos
- Node.js installed — node >= 18 — the skill verifies this
- A built static site — Run your framework's build (e.g. npm run build)
Flujo
-
Ask Claude to deploy
Build this Astro site and deploy it with pinme.✓ Copiado
→ Claude runs the build, detects dist/, installs pinme if missing, runs the upload
-
Get the URL
(no prompt — just wait)✓ Copiado
→ Preview URL returned in the chat
Resultado: A shareable IPFS-hosted preview.
Errores comunes
- 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
Cuándo usarlo: You're iterating on a prototype and want every version to be linkable.
Flujo
-
Build and deploy after each change
Every time I say 'ship', rebuild and upload via pinme, then post the URL.✓ Copiado
→ Claude develops a rhythm of build → deploy → URL
Resultado: A linkable preview history of your iterations.
Errores comunes
- IPFS CIDs change on every deploy (expected) — Use ENS or DNSLink if you want a stable URL
Combinaciones
Combínalo con otros MCPs para multiplicar por 10
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.✓ Copiado
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.✓ Copiado
Coste y límites
Lo que cuesta ejecutarlo
- Cuota de API
- PinMe free tier with usage caps; check pinme.eth for current limits
- Tokens por llamada
- Trivial — the skill is small
- Monetario
- Free tier available; paid tiers for larger / more persistent pins
- Consejo
- Let test previews expire; only pin the production URL long-term.
Seguridad
Permisos, secretos, alcance
Almacenamiento de credenciales: No credentials required for anonymous uploads. Optional account key for pinning persistence.
Salida de datos: 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.
Resolución de problemas
Errores comunes y soluciones
pinme: command not found
The skill should install it; run npm i -g pinme manually if blocked.
Verificar: 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.
Alternativas
pinme vs otros
| Alternativa | Cuándo usarla | Contrapartida |
|---|
| 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 |