Vibie MCP is an MCP (Model Context Protocol) server designed to enable AI clients (such as Claude Desktop, Cursor, etc.) to deploy local static folders to the Vibie platform, generating permanent *.vibie.page URLs.
Main Capabilities
- Deploy static folders: Upload a folder containing files such as index.html, style.css, js/, assets/, etc., to create a new Vibie site.
- Update existing sites: By reading the .vibie/site.json marker file in the folder, redeploy to the same site without manually specifying an identifier.
- Manage sites: List all sites under the account, or retrieve the metadata of a single site.
- Automatically skip irrelevant files: During upload, automatically ignore hidden files (such as .git, .vibie, .DS_Store) and the node_modules/ directory.
- Single-file support: If there is only one HTML file in the folder (with any name), it will be automatically renamed to index.html during upload.
Usage
- Installation and configuration: It is recommended to use a one-line automatic setup command, which automatically detects the configurations of Claude Desktop (Windows Store + APPDATA / macOS / Linux) and Cursor (~/.cursor/mcp.json), and adds the vibie entry. If the automatic setup is not applicable, you can manually add the configuration to the MCP configuration file (such as claude_desktop_config.json, ~/.cursor/mcp.json, etc.). After saving, you need to completely exit and restart the client.
- First authentication: When a tool is called for the first time, the server will start the OAuth 2.0 device authorization flow. The AI will receive an instruction similar to "Please open https://vibie.io/device?code=XXXX-YYYY in a browser, sign in with Google and click authorize, then let me retry". After authorization, the token will be saved in ~/.vibie/credentials.json (permissions 0600), and subsequent calls will automatically reuse it. Users can revoke the token at any time at https://vibie.io/settings/api .
- Available tools:
- vibie_create_site: Upload a folder and create a new site, automatically writing .vibie/site.json for subsequent updates.
- vibie_update_site: Redeploy to an existing site; if not specified, read the identifier from .vibie/site.json.
- vibie_list_sites: List the sites under the account.
- vibie_get_site: Retrieve the metadata of a single site based on the identifier.
Applicable Scenarios
- Developers who need to quickly deploy static HTML projects to the public internet and obtain permanent links.
- Those who use AI clients for development and want to complete deployment and updates directly through conversation.
- Scenarios that require frequent updates to static sites, using folder markers to simplify repeated deployments.
Limitations
- Each site is limited to a maximum of 100 MB, each upload is limited to a maximum of 500 files, and a single file is limited to a maximum of 25 MB (verified by the Vibie server).
- Only static files are supported; server-side logic is not involved.
- A Vibie account and network connection are required for authentication and deployment.
