Agent-native static site hosting — CLI, MCP server, and SDK for deploying to vibedrop.cc
Overview
Agent-native static site hosting. Tell your agent to deploy a folder — get a public URL in seconds. This repository contains the open-source clients. The hosting service itself runs at vibedrop.cc. Drop this into Claude Code, Cursor, Windsurf, or any agent that can read a URL: Read https://vibedrop.cc/skill.md and follow the instructions to set up VibeDrop. 1. Any agent that can fetch URLs will work. 2. It reads skill.md, runs npm i -g @vibedrop/cli, and provisions an anonymous API key. No signup, no credit card. 3. Point at any folder with an index.html — a dist/, a loose HTML bundle, or whatever the agent just wrote. - "Put ./site online and text me the link." - "Build this and deploy the output to VibeDrop." - "Deploy the landing page you just wrote." Anything with an index.html at its root: - — dist/, out/, build/ from Vite, next export, Astro, SvelteKit, CRA, etc. - — a hand-written index.html plus its assets, a single-file mockup, an AI-generated landing page.
README
VibeDrop
Agent-native static site hosting. Tell your agent to deploy a folder — get a public URL in seconds.
- Website: https://vibedrop.cc
- Skill:
skill.md - CLI:
@vibedrop/cli - MCP server:
@vibedrop/mcp - SDK:
@vibedrop/sdk
This repository contains the open-source clients. The hosting service itself runs at vibedrop.cc.
Quick start — paste one prompt to your agent
Drop this into Claude Code, Cursor, Windsurf, or any agent that can read a URL:
Read https://vibedrop.cc/skill.md and follow the instructions to set up VibeDrop.
Three steps, ~30 seconds:
- Paste the prompt. Any agent that can fetch URLs will work.
- Agent installs itself. It reads
skill.md, runsnpm i -g @vibedrop/cli, and provisions an anonymous API key. No signup, no credit card. - Ask for a URL. Point at any folder with an
index.html— adist/, a loose HTML bundle, or whatever the agent just wrote.
Then say something like:
- “Put
./siteonline and text me the link.” - “Build this and deploy the output to VibeDrop.”
- “Deploy the landing page you just wrote.”
What counts as a deployable folder?
Anything with an index.html at its root:
- Framework build output —
dist/,out/,build/from Vite,next export, Astro, SvelteKit, CRA, etc. - Plain HTML — a hand-written
index.htmlplus its assets, a single-file mockup, an AI-generated landing page. - Files your agent just wrote — “deploy the folder you just made.”
- Chrome extension or Electron local pages — any directory of static HTML.
VibeDrop serves static files only. If your framework needs a build step, run it first and point at the output directory.
Alternatives
MCP server
If you’d rather the agent call deploy as a native tool (instead of shelling out to the CLI), install the MCP server:
claude mcp add vibedrop -- npx @vibedrop/mcp
Cursor / Windsurf — add to your MCP config:
{
"mcpServers": {
"vibedrop": { "command": "npx", "args": ["-y", "@vibedrop/mcp"] }
}
}
CLI (humans)
npx @vibedrop/cli deploy ./dist
SDK (Node)
import { VibedropClient, packDir } from "@vibedrop/sdk";
const client = new VibedropClient({ apiKey: process.env.VIBEDROP_KEY });
const zip = await packDir("./dist");
const { site } = await client.deploy(zip);
console.log(site.url);
Development
pnpm install
pnpm build
pnpm typecheck
License
MIT — see LICENSE.
Install
npx -y @vibedrop/mcpConfiguration
{
"mcpServers": {
"vibedrop": { "command": "npx", "args": ["-y", "@vibedrop/mcp"] }
}
}