The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Vibie MCP listing page.
MCP server for Vibie — deploy static folders to permanent *.vibie.page URLs from Claude Desktop / Cursor / any MCP-compatible client.
Auto-detects Claude Desktop (Windows Store + APPDATA / macOS / Linux) and Cursor (~/.cursor/mcp.json) configs, then adds the vibie entry. Restart the client and you're done.
If auto setup doesn't fit your client, add this to your MCP config (claude_desktop_config.json, ~/.cursor/mcp.json, etc.):
After saving, fully quit and restart your client.
On first tool call, the server initiates an OAuth 2.0 Device Authorization Grant. Your AI will receive instructions like:
Please open https://vibie.io/device?code=XXXX-YYYY in a browser, sign in with Google, and click Authorize. Then ask me to try again.
After authorizing in the browser, ask your AI to retry the same request. The server stores a token in ~/.vibie/credentials.json (chmod 0600) and reuses it for future calls.
You can revoke the token anytime at https://vibie.io/settings/api.
vibie_create_site — Upload a folder and create a new Vibie site. Auto-writes .vibie/site.json in the folder so future updates use the same site.vibie_update_site — Re-deploy to an existing site. Reads slug from .vibie/site.json if not specified.vibie_list_sites — List sites under your account.vibie_get_site — Metadata for one site by slug.What gets uploaded from a folder:
index.html + style.css + js/, assets/, etc — all included.git, .vibie, .DS_Store) — automatically skippednode_modules/ — skippedA single HTML file (any name) also works — it gets auto-renamed to index.html on upload.
| Variable | Default | Purpose |
|---|---|---|
VIBIE_API_BASE | https://vibie.io | Override for local dev (http://localhost:3000) |
MIT