Skip to main content
Glama
shdomi8599

vibie-mcp

by shdomi8599

Related Servers

Alternatives to vibie-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Deploy any HTML project to a live public URL in seconds — directly from Cursor, Claude Code, or any MCP-compatible AI agent.
      2
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to publish static sites and build folders as live websites, push updates, provision and manage custom domains with DNS, and send transactional email. Ships as a local pip/uvx server that reads build folders directly, or as a hosted HTTP endpoint for Claude Code, Claude Desktop, and other MCP clients.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Publish websites from Claude, the terminal, or CI — drop a folder, get a link that doesn't expire. Wraps the nippy.host publish pipeline: create sites, update in place, read files, passwords, SEO settings, and visitor analytics.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Publishes HTML pages straight from your AI assistant to a shareable URL, then lets you manage them - update, list, search, fetch, and delete pages in a public or private workspace. Turns "share what I just made" into a single tool call from Claude, Cursor, or any MCP client.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for VibeKit — build, deploy, and manage hosted apps and chat with each app's persistent server-side AI agent from Claude Desktop, Cursor, or any MCP client. Every app gets its own agent and a live URL; bring your own Claude/OpenAI key or pay-as-you-go.
      36
      10 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Agent-native hosting: your agent deploys any folder to a live URL in one command — no account, no dashboard, no CAPTCHA — and hands the human a link plus a plain-language summary. Full deploy lifecycle as MCP tools (deploy, verify, logs, inspect, rollback), production approval human-only; static sites and full Node.js apps, open source (Apache-2.0).
      13
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create, get (single), list (all), and update. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'vibie_verb_noun' snake_case pattern. The prefix and structure are predictable and uniform.

    Tool Count5/5

    With 4 tools, the server is well-scoped for managing Vibie sites. Each tool earns its place without redundancy or insufficiency.

    Completeness4/5

    The set covers create, read (single and list), and update, which are core operations. Only missing delete, which is a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive