Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"vibie": {
"args": [
"-y",
"vibie-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Deploy HTML folders to vibie.page from Claude / Cursor — one-line install, OAuth, auto-update.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'vibie-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked vibie-mcp against OSV.dev.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / devops
MCP server for using the GitLab API
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
MCP Security Weekly
Get CVE alerts and security updates for io.github.shdomi8599/vibie-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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