vibekit-mcp

MCP server for VibeKit, deploy apps, manage hosting, and chat with AI agents from any MCP client.

This package is for VibeKit cloud/API access. It does not connect your local Claude Code instance to Telegram. For local-machine remote control, use vibekit-agent.

Use it remotely (no install)

VibeKit also runs as a hosted remote server, so clients that accept a remote MCP URL (claude.ai web connectors, ChatGPT, etc.) need no install:

https://mcp.vibekit.bot/mcp?api_key=vk_your_api_key_here

Paste that URL into your client's "custom connector" / "remote MCP server" field. Clients that let you set headers can instead send Authorization: Bearer vk_your_api_key_here and use the bare https://mcp.vibekit.bot/mcp. See Get an API key below.

Prefer a local stdio install (e.g. Claude Desktop)? Use the steps below.

Get an API key

Keys start with vk_. Two ways to get one:

• Instant, no signup: one request returns a key.

  curl -X POST https://vibekit.bot/api/v1/auth/register
  # Response: {"apiKey": "vk_...", "plan": "free", "credits": 0}

  Save the returned key and reuse it. Each call to /auth/register creates a brand-new account, so call it once, not per request.

• From your account: if you already use VibeKit, copy or regenerate your key in the web dashboard or the iOS app settings.

Installation

npm install -g vibekit-mcp

Setup

1. Get a VibeKit API key (see Get an API key above).

2. Add to your MCP client config (e.g. Claude Desktop) (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "vibekit": {
      "command": "vibekit-mcp",
      "env": {
        "VIBEKIT_API_KEY": "vk_your_api_key_here"
      }
    }
  }
}

3. Restart your MCP client

Available Tools

Hosting

Agent

Database

QA

Tasks

Account

Example Usage

Once configured, you can use prompts like:

• "Deploy my GitHub repo to VibeKit and create a new app"

• "Chat with the AI agent for my app about adding a contact form"

• "Show me the logs for my app and restart it if there are errors"

• "Enable a database for my app, then show me its schema and query the users table"

• "List my app's recent deploys and roll back to the last working one"

• "Run QA tests on my deployed app"

• "Check my VibeKit account balance and list my apps"

• "Create a weekly schedule to improve my app's performance"

Environment Variables

Related Packages

• vibekit-cli: terminal client for VibeKit cloud workflows

• vibekit-agent: Telegram bridge for local Claude Code on your own machine

Links

• VibeKit Website

• API Documentation

• Dashboard (view or regenerate your API key)

• GitHub

Privacy Policy

VibeKit's privacy policy: https://vibekit.bot/privacy

What this MCP server does with your data, concretely:

• Every tool call is forwarded to the VibeKit API (https://vibekit.bot/api/v1) over HTTPS, authenticated with the API key you configure. Tool inputs and outputs are processed by VibeKit to run your apps and agents, under the privacy policy above.

• The server itself keeps no state: nothing is written to disk, no analytics or telemetry are collected by this package, and your API key is read from configuration (VIBEKIT_API_KEY / the extension's key field) and sent only to vibekit.bot.

• Data retention, third-party sharing, and deletion are governed by the policy above. Questions: support@vibekit.bot.