Server data from the Official MCP Registry
Deploy HTML folders to vibie.page from Claude / Cursor — one-line install, OAuth, auto-update.
Deploy HTML folders to vibie.page from Claude / Cursor — one-line install, OAuth, auto-update.
Vibie MCP is a well-architected deployment tool with solid security practices. Authentication uses OAuth 2.0 Device Authorization Grant with proper token storage (0o600 permissions, env var support for base URL override). Code is clean with appropriate error handling and input validation. Permissions align with purpose: file I/O for folder uploads, network access for Vibie API, and env vars for configuration. No hardcoded secrets, malicious patterns, or dangerous operations detected. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
7 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-shdomi8599-vibie-mcp": {
"args": [
"-y",
"vibie-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP server for Vibie — deploy static folders to permanent *.vibie.page URLs from Claude Desktop / Cursor / any MCP-compatible client.
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.
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.
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.
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.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
What gets uploaded from a folder:
index.html + style.css + js/, assets/, etc — all included.git, .vibie, .DS_Store) — automatically skippednode_modules/ — skippedA single HTML file (any name) also works — it gets auto-renamed to index.html on upload.
| Variable | Default | Purpose |
|---|---|---|
VIBIE_API_BASE | https://vibie.io | Override for local dev (http://localhost:3000) |
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.