VibeKit MCP Server

by vibekit-bot Your server? Claim it

answering

VibeKit is answering right now. Last checked 1 min ago. It exposes 36 tools. Last commit 29 Oct 2026.

Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.

Uptime history 91 days of history · worst day 95%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

475 ms

Response time

average over 24h

Stars

last commit 29 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 October 2026. No other catalogue keeps this.

29 Oct a tool changed the parameters it asks for vibekit_create_schedule

Nothing serious here today

Today is the operative word: we check VibeKit every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add vibekit-mcp --transport http https://mcp.vibekit.bot/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.vibekit.bot/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 36

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

vibekit

vibekit_account

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

vibekit_agent_history

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

vibekit_agent_status

Check whether an app's AI agent is idle or working, and get its LIVE progress. Returns activity.status = the current human-readable build step (e.g. 'editing index.html', 'deploying'), activity.steps = the steps so far, and activity.done = whether the turn finished. Poll this every few seconds while a build is running and relay activity.status to the user so they see progress. Once activity.done is true the response also includes liveCheck = a server-side fetch of the deployed page ({ url, ok, httpStatus, title }); use it to confirm the app is live and renders — do NOT curl/fetch the URL yourself, your sandbox may block it.

vibekit_app_env

Get the environment variables configured for an app (names and values). Read-only — use vibekit_set_env to change them.

vibekit_app_logs

Fetch recent container/application logs for an app. Use this to debug crashes, errors, or a deploy that isn't serving.

vibekit_cancel_task

Cancel a running task by taskId. No-op if it has already finished.

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. Use for 'build/make a change to my app' requests. If the agent finishes quickly you get its reply directly. Otherwise you get status:'working' — do NOT resend; instead give the user LIVE progress: poll vibekit_agent_status every few seconds and relay the current step from activity.status ('editing the homepage…', 'deploying…') until activity.done, then read vibekit_agent_history for the final reply.

vibekit_create_app

Create a new hosted app from a starter template and deploy it live at <subdomain>.vibekit.bot. Call vibekit_list_templates first to pick a valid template. To deploy existing code from a GitHub repo instead, use vibekit_deploy.

vibekit_create_schedule

Create a recurring coding task that the AI runs automatically on a cron schedule (e.g. a weekly SEO pass). Use for 'every Monday, do X to my repo' requests.

vibekit_database_status

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

vibekit_db_query

Run a read-only SQL query against an app's Postgres database and return up to 200 result rows. SELECT only — writes and DDL (INSERT/UPDATE/DELETE/ALTER/DROP/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the agent make data or schema changes. Call vibekit_db_schema first to learn the tables. SQL string, max 5000 chars.

vibekit_db_schema

Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.

vibekit_db_table

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

vibekit_delete_app

Permanently delete a hosted app — stops the container and removes its workspace, database, env vars, and subdomain. Irreversible (the GitHub repo is NOT touched). Confirm with the user before calling.

vibekit_delete_schedule

Delete a scheduled recurring task by scheduleId. Confirm with the user first.

vibekit_deploy

Deploy a GitHub repo to VibeKit hosting, live at <subdomain>.vibekit.bot (Fargate container behind nginx, SSL automatic). Use when the code already lives in a GitHub repo; for a starter template instead use vibekit_create_app.

vibekit_enable_database

Provision a Postgres database for an app (idempotent — safe if already enabled). Required before the vibekit_db_* tools work. Note: free-tier apps need the $3/mo Database add-on.

vibekit_get_app

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

vibekit_get_skill

Fetch the full content of a specific skill — implementation patterns, code examples, and best practices for a domain. Fetch on-demand when you need guidance on a specific topic.

vibekit_get_task

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

vibekit_list_apps

List all hosted apps in your VibeKit account, each with its id, subdomain, status, and live URL. Start here to get an appId for the other app tools.

vibekit_list_deploys

List an app's recent deploys, newest first, with status and commit info. Find a deployId here to pass to vibekit_rollback_deploy.

vibekit_list_schedules

List all of the account's scheduled recurring tasks.

vibekit_list_skills

List available implementation skills (IDs, names, descriptions, tags) from the VibeKit skills registry. Discover skills here before fetching one with vibekit_get_skill.

vibekit_list_tasks

List recent coding tasks, optionally filtered by status.

vibekit_list_templates

List the starter templates available to vibekit_create_app (e.g. landing, dashboard, blog, saas, crud-api). Call this before vibekit_create_app to choose a valid template.

vibekit_qa_status

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

vibekit_redeploy

Redeploy an existing app to pull and ship the latest code. Use after pushing changes to the app's GitHub repo.

vibekit_restart_app

Restart a hosted app's container. Use when an app is wedged, or to apply changed environment variables.

vibekit_rollback_deploy

Roll an app back to a previous deploy (get the deployId from vibekit_list_deploys). The container restarts on the rolled-back build; reversible by rolling forward again.

vibekit_run_qa

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

vibekit_set_env

Set or update environment variables for an app (merges with existing). The app must be restarted or redeployed for changes to take effect.

vibekit_start_app

Start a stopped hosted app's container. Use to bring an app stopped via vibekit_stop_app back online.

vibekit_stop_app

Stop a hosted app's container. The app stays in your account and can be brought back with vibekit_start_app. Use to take an app offline without deleting it.

vibekit_submit_task

Submit an autonomous coding task. The AI writes the code, commits to GitHub, and (by default) deploys to <subdomain>.vibekit.bot. Returns a taskId — poll vibekit_get_task or block with vibekit_wait_for_task. Use for 'build X' or 'change X' work against a repo.

vibekit_wait_for_task

Block until a submitted task finishes (or the timeout), polling every 5 seconds, then return its result. Use right after vibekit_submit_task when you want the final result inline.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.vibekit.bot/mcp	streamable-http	answering	442 ms	1 min ago

Alternatives to VibeKit

same job, measured the same way

Tv MCP

by skdonthi

Build, deploy, and debug web apps on Samsung Tizen and LG webOS Smart TVs from any MCP client

10 installs/wk local only

Hatchable

by hatchable

Build, deploy, and host full-stack web apps from any MCP client. DB, auth, storage, cron included.

answering

Air Pipe

by airpipe

Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.

19 tools answering

Aurora

by aurora

Create, edit, preview, and deploy full-stack web apps to a live URL from any MCP client.

answering

Imperal MCP

by imperalcloud

Build, validate, smoke-test & deploy Imperal declarative IR apps from any LLM or agent.

5 483 installs/wk local only

MaShop MCP

by mashop

Build, deploy and manage MaShop e-commerce projects from Claude, Cursor or any MCP client.

answering

Nora

by solomon2773

Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.

65 installs/wk local only

Connic

by connic

Build, test, deploy, and operate Connic agents.

answering

VibeKit — questions

Answers built from our own checks of this server.

What can VibeKit do?

It exposes 36 tools, read directly from the server on our last check. Among them: vibekit_account, vibekit_agent_history, vibekit_agent_status, vibekit_app_env, vibekit_app_logs, vibekit_cancel_task and 30 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is VibeKit working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 475 ms. The bar chart above shows every period we have measured.

How do I connect VibeKit?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does VibeKit need an API key?

No. VibeKit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 36 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is VibeKit?

It answers our handshake in 475 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is VibeKit open source?

The code is open source: it is published under the MIT licence, written in TypeScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.vibekit.bot, which runs on its operator's own terms.