Vibie MCP

What shdomi8599/vibie-mcp MCP server does

The shdomi8599/vibie-mcp MCP server publishes static website content to permanent *.vibie.page URLs. It is intended for folders containing an index.html, stylesheets, JavaScript, images, and other static assets. A single HTML file with another filename is also accepted and is renamed to index.html during upload.

A new deployment creates a Vibie site and returns its URL. The server also writes .vibie/site.json into the source folder, allowing subsequent deployments to target the same site without asking for the slug again. Existing content can therefore be refreshed after local changes.

How it works

The server exposes four MCP tools:

• vibie_create_site uploads a folder and creates a site.
• vibie_update_site redeploys a folder to an existing site.
• vibie_list_sites lists sites associated with the account.
• vibie_get_site retrieves metadata for a site by slug.

On the first tool call, shdomi8599/vibie-mcp MCP server starts an OAuth 2.0 Device Authorization Grant flow. The client receives a Vibie URL and a device code; the user opens that URL, signs in with Google, and authorizes access. The resulting token is stored at ~/.vibie/credentials.json with restrictive file permissions and reused for later requests. Tokens can be revoked from Vibie's API settings.

Setup and configuration

The recommended setup command is:

npx vibie-mcp setup

This setup process detects Claude Desktop configuration locations on Windows, macOS, and Linux, as well as Cursor's ~/.cursor/mcp.json, then adds a vibie MCP entry. Clients must be fully restarted after configuration changes.

Manual configuration runs the server with npx and the -y vibie-mcp arguments. The documented configuration works with Claude Desktop, Cursor, and other MCP-compatible clients. The optional VIBIE_API_BASE environment variable changes the Vibie API base URL; its default is https://vibie.io, and the README gives http://localhost:3000 as a local-development example.

Tools and capabilities

Deployments include normal static assets such as HTML, CSS, JavaScript, and asset directories. Hidden files including .git, .vibie, and .DS_Store are skipped automatically, as is node_modules/.

Vibie validates these upload limits: 100 MB per site, 500 files per upload, and 25 MB per individual file. The server does not describe support for dynamic application runtimes or server-side code; its documented use is static folder deployment.

Limitations and notes

The first authenticated request requires browser interaction and a Vibie account sign-in. Updating without a specified slug depends on the presence of .vibie/site.json in the folder. The documented deployment limits are enforced by Vibie's server, so folders exceeding them will not upload successfully.

The shdomi8599/vibie-mcp MCP server is released under the MIT license. Its repository documents OAuth authentication and the Vibie service endpoint, but it does not state whether Vibie hosting itself has usage charges.