Developer Tools

vibekit.bot

Manages VibeKit hosted apps, including listing, creating, deploying, and retrieving details.

1 endpoint36 known toolsFirst detected June 5, 2026Last detected July 25, 2026

ENDPOINT 1

https://mcp.vibekit.bot/mcp

No auth detected

MCP server metadata

Name: vibekit
Version: 0.8.0

Capabilities

tools

Server instructions

VibeKit hosts, deploys, and operates web apps and AI coding agents. Each app runs in its own container at <subdomain>.vibekit.bot with optional Postgres, logs, env vars, and automated QA, plus a built-in AI agent that can edit the app's code. Use these tools whenever the user wants to: deploy a GitHub repo or starter template and get a live URL; list, inspect, restart/stop/start, or delete hosted apps; read logs to debug; manage env vars; enable and query an app's Postgres (call vibekit_db_schema before writing SQL); list or roll back deploys; run or check QA; chat with an app's AI agent to change its code; or submit/schedule autonomous coding tasks that commit to GitHub and deploy. Most tools key off an appId — call vibekit_list_apps first to resolve one. Confirm destructive actions (vibekit_delete_app, vibekit_delete_schedule, and write/DDL via vibekit_db_query) with the user before calling. Auth uses a VibeKit API key (vk_...) from the Telegram bot's /apikey command.

Known tools 36

vibekit_list_apps

List all hosted apps in your VibeKit account, each with its id, subdomain, status, and live URL.

Inferred read-only

vibekit_get_app

Get full details for one hosted app — status, subdomain/URL, repo, runtime, and database/domain config.

Inferred read-only

vibekit_create_app

Create a new hosted app from a starter template and deploy it live at <subdomain>.

Potential side effects

vibekit_list_templates

List the starter templates available to vibekit_create_app (e.

Inferred read-only

vibekit_deploy

Deploy a GitHub repo to VibeKit hosting, live at <subdomain>.

Inferred read-only

vibekit_redeploy

Redeploy an existing app to pull and ship the latest code.

Inferred read-only

vibekit_app_logs

Fetch recent container/application logs for an app.

Inferred read-only

vibekit_restart_app

Restart a hosted app's container.

Inferred read-only

vibekit_stop_app

Stop a hosted app's container.

Inferred read-only

vibekit_start_app

Start a stopped hosted app's container.

Inferred read-only

vibekit_app_env

Get the environment variables configured for an app (names and values).

Inferred read-only

vibekit_set_env

Set or update environment variables for an app (merges with existing).

Potential side effects

vibekit_delete_app

Permanently delete a hosted app — stops the container and removes its workspace, database, env vars, and subdomain.

Potential side effects

vibekit_chat

Send a message to an app's built-in AI coding agent, which reads, writes, and modifies the app's code and redeploys it.

Potential side effects

vibekit_agent_status

Check whether an app's AI agent is idle or working, and get its LIVE progress.

Inferred read-only

vibekit_agent_history

Get the recent chat history between the user and an app's AI agent.

Inferred read-only

vibekit_enable_database

Provision a Postgres database for an app (idempotent — safe if already enabled).

Inferred read-only

vibekit_database_status

Get an app's database status and connection info (whether it's provisioned, frozen, etc.

Inferred read-only

vibekit_db_schema

Get an app's database schema — every table and its columns.

Inferred read-only

vibekit_db_query

Run a read-only SQL query against an app's Postgres database and return up to 200 result rows.

Inferred read-only

vibekit_db_table

Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.

Inferred read-only

vibekit_list_deploys

List an app's recent deploys, newest first, with status and commit info.

Inferred read-only

vibekit_rollback_deploy

Roll an app back to a previous deploy (get the deployId from vibekit_list_deploys).

Inferred read-only

vibekit_run_qa

Kick off an automated QA run (headless-browser checks) against a hosted app.

Inferred read-only

vibekit_qa_status

Get the latest automated QA results and status for an app.

Inferred read-only

vibekit_submit_task

Submit an autonomous coding task.

Inferred read-only

vibekit_get_task

Get the status and result of a task submitted via vibekit_submit_task.

Inferred read-only

vibekit_list_tasks

List recent coding tasks, optionally filtered by status.

Inferred read-only

vibekit_wait_for_task

Block until a submitted task finishes (or the timeout), polling every 5 seconds, then return its result.

Inferred read-only

vibekit_cancel_task

Cancel a running task by taskId.

Inferred read-only

vibekit_create_schedule

Create a recurring coding task that the AI runs automatically on a cron schedule (e.

Potential side effects

vibekit_list_schedules

List all of the account's scheduled recurring tasks.

Inferred read-only

vibekit_delete_schedule

Delete a scheduled recurring task by scheduleId.

Potential side effects

vibekit_account

Get VibeKit account info: plan, credit balance, and usage.

Inferred read-only

vibekit_list_skills

List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry.

Inferred read-only

vibekit_get_skill

Fetch the full content of a specific skill — implementation patterns, code examples, and best practices for a domain.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vibekit]
url = "https://mcp.vibekit.bot/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vibekit": {
      "type": "http",
      "url": "https://mcp.vibekit.bot/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vibekit
Remote MCP URL: https://mcp.vibekit.bot/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vibekit": {
      "url": "https://mcp.vibekit.bot/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vibekit": {
      "type": "http",
      "url": "https://mcp.vibekit.bot/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vibekit",
  "transport": "streamable-http",
  "url": "https://mcp.vibekit.bot/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.