Command Palette

Search for a command to run...

UnylyUnyly
Browse all

Vibie

FreeNot checked

Deploy static HTML folders to permanent vibie.page URLs from Claude, Cursor, or any MCP client. One-line auto-install wires up the config, OAuth device-flow han

GitHubEmbed

About

Deploy static HTML folders to permanent vibie.page URLs from Claude, Cursor, or any MCP client. One-line auto-install wires up the config, OAuth device-flow handles auth, and a folder marker lets repeat deploys skip the slug.

README

MCP server for Vibie — deploy static folders to permanent *.vibie.page URLs from Claude Desktop / Cursor / any MCP-compatible client.

Install

One-line auto setup (recommended)

npx vibie-mcp setup

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.

Manual config

If auto setup doesn't fit your client, add this to your MCP config (claude_desktop_config.json, ~/.cursor/mcp.json, etc.):

{
  "mcpServers": {
    "vibie": {
      "command": "npx",
      "args": ["-y", "vibie-mcp"]
    }
  }
}

After saving, fully quit and restart your client.

First-time auth

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.

Tools

  • 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.

How AI typically uses it

You: "Deploy this folder to vibie"
AI: → vibie_create_site({ folder: "." })
    → Returns: https://my-folder-x7f2.vibie.page

You: "Push my changes"
AI: Detects .vibie/site.json
    → vibie_update_site({ folder: "." })
    → Same URL, new content

Folder structure

What gets uploaded from a folder:

  • index.html + style.css + js/, assets/, etc — all included
  • Hidden files (.git, .vibie, .DS_Store) — automatically skipped
  • node_modules/ — skipped
  • Limits: 100 MB per site, 500 files per upload, 25 MB per file (Vibie's server validates)

A single HTML file (any name) also works — it gets auto-renamed to index.html on upload.

Env

Variable Default Purpose
VIBIE_API_BASE https://vibie.io Override for local dev (http://localhost:3000)

License

MIT

from github.com/shdomi8599/vibie-mcp

Install Vibie in Claude Desktop, Claude Code & Cursor

Recommended · one command, every IDE
unyly install vibie-mcp

Installs into Claude Desktop, Claude Code, Cursor & VS Code — handles npx, uvx and build-from-source repos for you.

First time? Get the CLI: curl -fsSL https://unyly.org/install | sh

Or configure manually

Run in your terminal:

claude mcp add vibie-mcp -- npx -y vibie-mcp

FAQ

Is Vibie MCP free?

Yes, Vibie MCP is free — one-click install via Unyly at no cost.

Does Vibie need an API key?

No, Vibie runs without API keys or environment variables.

Is Vibie hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Vibie in Claude Desktop, Claude Code or Cursor?

Open Vibie on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare Vibie with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All ai MCPs