English Français العربية

io.github.shdomi8599/vibie-mcp

Official registry Cloud and DevOps

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

Source code Documentation

What can you do with io.github.shdomi8599/vibie-mcp?

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package vibie-mcp
Claude Code 
claude mcp add vibie-mcp -- npx -y vibie-mcp@0.2.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "vibie-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "vibie-mcp@0.2.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. vibie-mcp
  2. Install
  3. First-time auth
  4. Tools
  5. How AI typically uses it
  6. Folder structure
  7. Env
  8. License

vibie-mcp

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

Install

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

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

License

MIT

Frequently asked questions

What is io.github.shdomi8599/vibie-mcp?

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

How do I install io.github.shdomi8599/vibie-mcp?

It runs on your machine. In Claude Code: claude mcp add vibie-mcp -- npx -y vibie-mcp@0.2.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.shdomi8599/vibie-mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.shdomi8599/vibie-mcp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.shdomi8599/vibie-mcp?

It is published by shdomi8599. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.