Vibie Mcp

io.github.shdomi8599Published by GitHub account shdomi8599v0.2.2Updated Oct 24, 2026

Deploy HTML folders to vibie.page from Claude / Cursor — one-line install, OAuth, auto-update.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Deploys a local HTML folder or single HTML file to a permanent public *.vibie.page URL from an MCP client.

What you can do
This server exposes tools to publish static web content to the Vibie hosting service. vibie_create_site uploads a folder and creates a new site, returning its public URL and writing a .vibie/site.json marker so later updates target the same site. vibie_update_site re-deploys content to an existing site, and vibie_list_sites and vibie_get_site read account site listings and metadata. Hidden files and node_modules are skipped, and a lone HTML file is renamed to index.html on upload.
When to use it
Use it when you want an assistant to publish a static site or a single HTML page straight from a local project folder and get a shareable link, and to push later edits to the same URL without manual upload steps.
Requirements
Runs locally over stdio, typically launched with npx, so Node.js and network access are needed. First use triggers an OAuth 2.0 device authorization: you open a browser link, sign in with Google, and approve access; the token is stored in ~/.vibie/credentials.json. An optional VIBIE_API_BASE variable overrides the API endpoint.
Before you install
The server uploads the contents of the chosen folder to Vibie's servers, so anything in that folder becomes public at a *.vibie.page URL; hidden files and node_modules are skipped but other files are not filtered. It writes a .vibie/site.json file into the deployed folder and stores an OAuth token in ~/.vibie/credentials.json, which can be revoked from the Vibie account settings. Uploads are limited to 100 MB per site, 500 files, and 25 MB per file.

Installation

In SourceWeft

  1. Open Vibie Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

vibie-mcp

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)

sh
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.):

json
{  "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

VariableDefaultPurpose
VIBIE_API_BASEhttps://vibie.ioOverride for local dev (http://localhost:3000)

License

MIT

Source: README.md at commit 47e3e72

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts